Hi--

     We don't need a system dictionary at all. We can make each class
responsible for its own name literal, use subclass/metaclass references
for reachability, and make all other globals the responsibility of some
class. Every class can have any name; the execution machinery doesn't
care. Other metadata about classes (e.g., author) can be used to
disambiguate their names when compiling sources. We can store all that
metadata in a module system, to manage the history of all versions of
all classes and methods in the system.

     The Naiad module system that I wrote[1] implements this. I've
adapted it to the latest Squeak and plan to release it this month.


-C

[1] http://thiscontext.com/naiad

--
Craig Latta
Black Page Digital
Amsterdam | San Francisco
craig at blackpagedigital.com
+31   6 2757 7177 (SMS ok)
+ 1 415  287 3547 (no SMS)