Yes thats exactly what I meant with my reply. I was not so sure though about the exact role of globals in pharo and how many problems their removal would cause internally. ΣÏÎ¹Ï 14 Îεκ 2013 9:39 μ.μ., ο ÏÏήÏÏÎ·Ï "Craig Latta" <craig@netjam.org> ÎγÏαÏε:
Hi Norbert--
Class names are globals. A class is registered in a global namespace by its name. Names need to be looked up. How should it work in another way?
Get rid of globals. Make the root classes elements of the special objects array (Object already is), and look up classes through that. Make everything else that used to be a global (like Transcript) the responsibility of some class, and use them by sending messages. This also makes the modularization straightforward.
There's no need for a system dictionary. It was a profound and long-lived mistake.
-C
-- Craig Latta www.netjam.org/resume +1 510 984 8117 (Skype rings this until 31 January 2014)