<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 1, 2014 at 3:59 PM, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span> wrote:<br>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><span style="color:rgb(34,34,34)">Why would we convert class variables to Globals? Do you mean we'd</span><br>
</div></div>
represent the bindings of class variables as Globals (because the code<br>
referencing the class variable has no way of knowing whether it's<br>
referencing a class variable or a Really True global? If so, OK.</blockquote><div><br></div><div>Yeah, I just mean use Global instance for the bindings instead of Associations. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I guess "Global" might need a different name then. It's really<br>
SomethingThatsNotAClassOrTraitButAvailableToMe.<br></blockquote><div><br></div><div>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. </div>
<div><br></div><div>Colin</div><div><br></div></div></div></div>