<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Mar 9, 2013 at 6:48 AM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com" target="_blank">siguctua@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">Well, maybe it's an overkill .. it is mainly about speed and reusing<br>
VM's lookup mechanism<br>
for searching a name over multiple scopes (when you have namespaces<br>
with imports).<br>
<br>
On a first run, you will replace<br>
"read value of <binding>" bytecode with " send #value to <binding>"<br>
but that implies having a binding at compile time (you must lookup for<br>
a name at compile time).<br>
It also means that you won't change anything semantically: even though<br>
you sending a message,<br>
you still accessing the very same state which you bound early at compile time.<br></blockquote><div><br></div><div>Right. The lookup happens at compile time. When the method is actually executed, we're just fetching the value from the binding we found at compile time. I don't see how that's going to be slow. In the most common case, a class reference, it's not even a message send, because we have a dedicated bytecode. For global variables, it'll be two message sends: we send #value to the alias binding, which then sends #value on to the canonical binding in the environment's "contents" dictionary. </div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Then, i wonder, if such change is actually worth doing. Because if you<br>
don't do lookup dynamically,<br>
then there is no change.<br></blockquote><div><br></div><div>Sure there is. We still bind names at compile time, but we have changed the way names are resolved. </div><div><br></div><div>Colin</div></div></div></div>