<br><br><div class="gmail_quote">On Wed, Feb 3, 2010 at 9:51 PM, Andreas Raab <span dir="ltr"><<a href="mailto:andreas.raab@gmx.de">andreas.raab@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Eliot Miranda wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Andreas,<br>
<br>
one rationale for ...<br>
do: [| blockScope | ... blockScope := ...]<br>
...<br>
over<br>
| methodScope |<br>
...<br>
do: [... methodScope := ...]<br>
is that if ever one adds parallel do to the language the former continues to work whereas the latter breaks. Personally I find declaring things at method scope that are truly block scope bad style and not forward looking. Yes, the auto declare facility is poor in this regard but it's fixable.<br>
</blockquote>
<br></div>
The change wasn't intentional, I was merging a whole bunch of stuff from Juan and wasn't going to rewrite every method manually to push the temps into the proper place. You'll have to accept that when you merge external code you get some of that style along with your own. Not much to do unless you fix the tools to do The Right Thing by default.<br>
</blockquote><div><br></div><div>Ah! Hush my mouth!!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Cheers,<br><font color="#888888">
- Andreas<br>
<br>
<br>
</font></blockquote></div><br>