ah, ok, I imagine that but what it was a bit of a surprise for me is that it is implemented in Object... I mean, I know that halt is also implemented in Object and it is the natural place to implement those messages, but if we want to build a "modular" system, messages like halt, error, etc should be removed from Object and seeing that Object is growing in its responsibilities with these messages I think that goes against that path... of course, if you decided that the trade off deserves it, fine by me...�
I was thinking that halt for example could be implemented in MethodContext (or ContextPart) so you can write something like "thisContext halt" and not couple Object with Halt (of course we would be coupling MethodContext with Halt, but it is a smaller coupling)... or just remove halt as a message and force everybody to just write "Halt signal" of "Halt signalOnce" etc. I mean, why Object implements halt? I know it is handy to do "self halt" but also as handy as "Halt signal"... the only reason I see to implement halt in Object is the possibility for any subclass to override that message, but I haven't seen that in my years of smalltalker...

Anyway, just a late's Friday thought :-)

PS: A #haltIf: aBlock message would be handy too :-)



On Fri, Oct 1, 2010 at 8:53 AM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:
+ 1 really really important

On Sep 30, 2010, at 11:38 PM, Alexandre Bergel wrote:

> I used haltOnce quite often when I had to debug the rendering facilities in Mondrian.
> Putting "self halt" in a drawOn: method can easily freeze your image.
>
> Alexandre
>
>
>
> On 30 Sep 2010, at 17:18, Hernan Wilkinson wrote:
>
>> Hi,
>> when are these messages used? what are the scenarios?
>> I just want to understand why they are there...
>>
>> --
>> Hern�n Wilkinson
>> Agile Software Development, Teaching & Coaching
>> Mobile: +54 - 911 - 4470 - 7207
>> email: hernan.wilkinson@10Pines.com
>> site: http://www.10Pines.com
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel �http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project



--
Hern�n Wilkinson
Agile Software Development, Teaching & Coaching
Mobile: +54 - 911 - 4470 - 7207
email: hernan.wilkinson@10Pines.com
site:�http://www.10Pines.com