> > Which advantages do you see in removing classVars and pool vars?
> 
> You unify them. You do not have cassVariable and poolVariable 
> to explain and have instance variable, class instance, and class 
> variable AND pool. Just "global" variables in a namespace and
> instance and class instance variables.

But how do you deal with (intentional) sharing and (intentional) locality?
E.g., taking TextConstants - would they end up in a global name space where
(for example) Cr is the same as String Cr or similar?

> Then Pool are really ugly and static (try to change the value of
> a pool variable and see how the method refering to it can break :))

How do "namespace variables" address this problem?

> > What do you mean by namespace variables? There are no namespaces
> > in Squeak yet?
> 
> Yes there are, SystemDictionary is a namespace and environment its 
> subclass it clearly that. This is just that nobody use that except
> henrik for his module stuff.

Can you say a few words about what would be different/better when using this
approach compared to class variables and pools? Somehow it seems to me
you're just exchanging two equivalent concepts.

Cheers,
  - Andreas