On Wed, Jan 1, 2014 at 3:59 PM, Frank Shearar <frank.shearar at gmail.com>wrote:


> Why would we convert class variables to Globals? Do you mean we'd
> represent the bindings of class variables as Globals (because the code
> referencing the class variable has no way of knowing whether it's
> referencing a class variable or a Really True global? If so, OK.


Yeah, I just mean use Global instance for the bindings instead of
Associations.


> I guess "Global" might need a different name then. It's really
> SomethingThatsNotAClassOrTraitButAvailableToMe.
>

It's true the Global isn't strictly accurate, but that's true of bindings
in an environment too. The effect of Environments is that nothing is global
any more. VisualWorks uses the term SharedVariable for everything that's
accessed via a binding (i.e., all variables that are not  temps or instance
variables). That's accurate, I guess, but kind of awkward.

Colin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20140101/2296e7c0/attachment.htm