On Feb 18, 2010, at 12:59 PM, Miguel Enrique Cobá Martinez wrote: > El jue, 18-02-2010 a las 12:18 -0800, Dale Henrichs escribió: >> Gemstone uses an order list of dictionaries for global lookup. Each user can >> change the order of the list or insert their own dictionaries into the list >> ... makes for quite a bit of flexibility.... you can load code into a >> particular dictionary...and the global resolution is at compile time (you >> can do lookup at runtime if you wish). >> >> The advantage is that the code itself has no namespace artifacts at all. >> >> I'm mentioning this as a point of information more than a serious suggestion >> that Pharo adopt such an approach, though:) > > Why not, if it has been proved for a long time in Gemstone, shouldn't be > sensible to create something similar for Pharo? Or it uses some kind of > proprietary technology from Gemstone?
You've heard the phrase, "Imitation is the sincerest form of flattery"? It's true! We would be delighted to see Pharo use a similar scheme for namespaces. Not only is it is an elegant approach, but its adoption by Pharo would ease the upgrade path to GemStone should the opportunity arise. For an overview of GemStone namespaces, see http://www.youtube.com/watch?v=z84n3O8YUsI. For more information see the Chapter 3 of the Programming Guide (http://seaside.gemstone.com/docs/GS64-ProgGuide-2.2.pdf). James Foster GemStone Systems, Inc. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
