[Pharo-project] Compiler pedantic about ifNotNil: argument

Stéphane Ducasse stephane.ducasse at inria.fr
Mon Oct 11 10:38:40 EDT 2010

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:

More information about the Pharo-dev mailing list