The question is how much will we have to backport. Because we do not have that horse power to do that for each little details. I would only backport really important fixes.
Stef On Dec 27, 2009, at 7:58 PM, Nicolas Cellier wrote: > 2009/12/27 Lukas Renggli <reng...@gmail.com>: >>> Julian: we (stef and I) have something we don't understand. The >>> implementation of ifEmpty: is like this in Pharo: >>> >>> Collection >> ifEmpty: aBlock >>> "Evaluate the block if I'm empty" >>> >>> self isEmpty ifTrue: [ ^aBlock value ] >> >> In Pharo 1.0rc1 it looks like this: >> >> Collection>>ifEmpty: aBlock >> "Evaluate the block if I'm empty" >> >> ^ self isEmpty ifTrue: aBlock >> >> Lukas >> > > It sounds stupid to return nil if not empty. > Should the change in 1.1 be backported ? > > Nicolas > >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> 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 _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
