[Pharo-project] Compiler pedantic about ifNotNil: argument

Levente Uzonyi leves at elte.hu
Mon Oct 11 10:53:32 EDT 2010

On Mon, 11 Oct 2010, Stéphane Ducasse wrote:

> On Oct 11, 2010, at 3:55 PM, Levente Uzonyi wrote:
>> On Mon, 11 Oct 2010, Stéphane Ducasse wrote:
>>>>> That "hack" is really cool IMO. The code is easily understood by anyone:
>>>> #(4 1 3 5 2) sort: #<=.
>>> yes in Moose people are using that a lot for scripting. Now the problem is that as soon
>>> as you need more you have to get a block.
>> Why is that a problem? You can use the symbol for simple cases and write blocks for the complicated ones.
> Indeed this is why we added Symbol>>value, even if I was against because been burned by Object>>value in some VW projects
> :)
> Now I do not see the point for ifNotNil: and for ifTrue:ifFalse:

I personally don't like the ifTrue:ifFalse: related changes, though it's 
a logical change. I probably won't use that feature though. But I like the 
monadic block <-> keyword selector substitution. Maybe the best is to add 
a setting/preference to the compiler.


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

More information about the Pharo-dev mailing list