+1 on the idea that this should be a whole lot slicker than it is. That said, Lukas' idea of keeping the relevant methods in an external package is certainly a way around the problem, and not even a bad way either. In fact, Dolphin's package system is VERY picky, and the way one usually gets it to relax is to create what I call "yet another package" so that things can load in the correct order.
FWIW, I am still trying to figure out whether MC is superior (more flexible) to (than) Dolphin's package load mechanism, or if I simply haven't yet been burned by what it fails to prevent. Bill ________________________________________ From: [email protected] [[email protected]] On Behalf Of Lukas Renggli [[email protected]] Sent: Thursday, June 17, 2010 7:25 AM To: [email protected] Subject: Re: [Pharo-project] Issue 2560 : Convenient methods from Grease for Strings > - If included with Pharo I suggest to rename all the methods, > otherwise we will run into big troubles with Seaside and other > projects that depend on Grease. > > > From a philosophical standpoint, I *hate* that. this means that as a > plattform, we can not > grow and improve our libraris anymore? > Shouldn't be the goal that useful extensions gets adopted by the core? I agree, from Pharo point of view. However, for any software built on top of Pharo it means troubles if Pharo suddenly implements the same methods. Lukas -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ 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
