<br><br><div class="gmail_quote">On Mon, Mar 9, 2009 at 3:58 PM, Keith Hodges <span dir="ltr"><<a href="mailto:keith_hodges@yahoo.co.uk">keith_hodges@yahoo.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">Keith Hodges wrote:<br>
> Keith Hodges wrote:<br>
><br>
>>> I will at some point push out a 3.8.22 VM that should put up a more<br>
>>> helpful dialog message, but people who have older VMs underfoot<br>
>>> should realize this behaviour should be an indication that perhaps<br>
>>> your VM is too old.<br>
>>><br>
>>><br>
>> Unfortunately the machine that I have designated for Bob to be an auto<br>
>> build/test server is a power-pc machine. What are the chances of a<br>
>> power-pc version of the closures vm?<br>
>><br>
>> just interested to know<br>
>><br>
>> Keith<br>
>><br>
> Ok I see it is designated beta1U for universal, so the problem lies<br>
> elsewhere!<br>
><br>
> Keith<br>
><br>
</div></div>OK so assigining to closure temporaries is no-longer allowed and flags a<br>
syntax error (not my code you understand)</blockquote><div><br></div><div>There is a preference that allows one to compile old code that does assign to block arguments. Its called allowBlockArgumentAssignment. Of course one can assign to closure temporaries. e.g.</div>
<div><br></div><div> self do: [:i| | j | j := i + 1. ...</div><div><br></div><div>But assigning to a block argument is dubious.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<font color="#888888"><br>
Keith<br>
<br>
<br>
</font></blockquote></div><br>