On Aug 30, 2010, at 4:45 35PM, Stéphane Ducasse wrote:
Ok so I can close the ticket then. :) Stef
Unless you want it as part of a 1.0 patch, yes. Cheers, Henry
---- On Mon, 30 Aug 2010 05:57:47 -0700 Levente Uzonyi wrote ----
I don't like the "magical" #asString, but you should discuss it with Andreas. Collection >> #ifEmpty: doesn't return nil, but the collection in the WebClient-Pharo package (and in Squeak), and I think it's better than nil.
I opened a ticked on this a few weeks back: http://code.google.com/p/pharo/issues/detail?id=2794
The ifEmpty:/ifNotEmpty: behavior of Squeak is demonstrably better and should be adopted.
heu... I evaluated the following in a pharo1.1-dev and 1.2-core:
(#(foo) ifEmpty:[#bar]) -> returns #(foo) (#() ifNotEmpty:[#bar]) -> returns #()
This seems to do what you propose? Johan _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Yes. Levente is right, I read the code of Andreas' wrong. Pharo 1.1/1.2 does this, so the override is for 1.0, where #ifEmpty: returns nil .
Cheers, Henry _______________________________________________ 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