<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 11, 2013 at 1:28 PM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I do wonder why Class>>bindingOf:environment: looks into the environment first, however. This means that a global variable would shadow an inherited class variable or pool variable, which is against my intuition of how scoping works. Does anyone know why this would be intended?</blockquote>
</div><br>When adding the environment: argument, I preserved the existing logic from Class>>bindingOf:, so as not to break anything while bootstrapping, but I agree it's wrong.</div><div class="gmail_extra"><br>
</div><div class="gmail_extra" style>I suspect that this is a holdover from the original Environments implementation, which lacked import/export between environments. Letting an environment shadow variables is the only way to override the superclass's environment. And without a way to do that, there can only be one environment!</div>
<div class="gmail_extra" style><br></div><div class="gmail_extra" style>Colin</div></div>