The problem is the side effects, is suddenly Boolean>>and: stops to be lazy. Possibly evaluating blocks that shouldn't be evaluated. Fernando
On Mar 5, 2010, at 8:22 AM, Igor Stasenko wrote: > Hello, > I just realized, that one can completely avoid using ifTrue/ifFalse > branches, but use #or: and #and: instead. > > a > b ifTrue: [ ... ] > could be written as: > a > b and: [ ... ] > > a > b ifFalse: [ ... ] > could be written as: > a > b or: [ ... ] > > and > a > b ifTrue: [ self foo ] ifFalse: [ self bar ] > could be written as: > > a > b and: [ self foo]; or:[ self bar ] > > :) > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > 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
