On Tue, 13 Apr 2010, Chris Muller wrote:

Peter mentioned VA, whose Set's swallow nil's.  Perhaps that's the
missing link in the communication here.  Igor is talking about
*Squeak*, which does not swallow nil's, it throws an error.

So, to "fix consequences instead of causes" in the case of Squeak, the
software would have to be doing something like:

  [ #(1 2 3 nil) asSet ]
    on: Error
    do: [ : err | "ignore it!" ]

which, deserves to break if it exists at all..


Squeak doesn't raise an error, but adds nil to the set (since 4.1), so there's no need for such tricks. If you want to ignore nils, just #reject: or #remove: them.


Levente

On Mon, Apr 12, 2010 at 10:33 AM, Stéphane Ducasse
<[email protected]> wrote:
igor

peter snippets was just a dull example. Peter mentioned that some people fix 
consequences instead of causes....


Stef
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to