On Jan 5, 2009, at 7:56 AM, Lukas Renggli wrote: >> I published to the inbox some cool collection extension methods that >> we use all the time in Moose. >> flatCollect:, collectAsSet:, and groupedBy: > > I think Squeak already has far too many of these methods. I would > rather like to see them all removed, than new ones added. As an author > and maintainer of many Smalltalk framework I experience daily the pain > such methods cause, as they are inherently non-portable not only > between smalltalk dialects but even between users of exactly the same > image. > (This rambles a bit, so bear with me... )
I agree with Lukas as far as what is the core system; I also used many of the unique and helpful methods available in Squeak and not in other Smalltalk implementations *as long as I know I'm not porting it another system*. With the ever improving Installer/Universes/SM system, can we not easily keep the core small and add collection extensions and other extensions as dependencies for a given package? Another option would be to change/rename the categories to denote ansi compliant methods, but since the categories metaphor is flat, methods can't be in more that one at a time. Could the OB smart filters be used in this way? Or would we have to implement some sort of tagging framework to be able to arbitrarily tag methods and classes, so methods can reside in appropriate categories and still be flagged as ANSI (among other things). I also agree with the sentiment (to a point) in the thread that ANSI is old and outdated, and why does Pharo have to be hobbled by that. From a practical matter, regardless of how old the ANSI standard is, it is the only standard we have, and when you are doing a framework like Seaside, or any number of others, compatibility with other Smalltalks where possible is extremely important. My 2 bits... - Brian _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
