<div dir="ltr">2013/7/29 tim Rowledge <span dir="ltr"><<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>></span><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
<br>
On 29-07-2013, at 1:54 AM, Clément Bera <<a href="mailto:bera.clement@gmail.com">bera.clement@gmail.com</a>> wrote:<br>
> - Lastly, does VW have the tempVector optimization for escaping write temporaries in their blockClosure ? It seems they have not (I don't see any reference to it in VW 7). Did Pharo/Squeak blocks earns a lot of speed or memory with this optimization ?<br>
<br>
</div>Assuming you're talking about what I think you are talking about, VW had it around 12years ago; I remember Eliot explaining it to me at least three times before I quite got it. I happened to be visiting with him for lunch on the day when it first worked well, IIRC.<br>
</blockquote><div><br></div><div>Thanks for your answer. So they have it. Actually on second thoughts it may be that blocks need the temp vector to work with the stack mapping: if a block outlive its homeContext, the homeContext variables may be overridden in the stack.</div>
<div><br></div><div>It is just that I see no reference to it in VW class comments. Perhaps it is only VM details hidden from the user.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
tim<br>
--<br>
tim Rowledge; <a href="mailto:tim@rowledge.org">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" target="_blank">http://www.rowledge.org/tim</a><br>
Useful Latin Phrases:- Re vera, potas bene = Say, you sure are drinking a lot.<br>
<br>
<br>
</blockquote></div><br></div></div>