<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 2, 2016 at 9:25 AM, tim Rowledge <span dir="ltr"><<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">{snipping lots}<br>
<span class="">> On 02-06-2016, at 8:19 AM, Levente Uzonyi <<a href="mailto:leves@caesar.elte.hu">leves@caesar.elte.hu</a>> wrote:<br>
><br>
>><br>
>> braceAtTheEndOfLine ifTrue: [<br>
>> (this isA: #Monstrosity) because:<br>
>> blocks are objects not syntax].<br>
><br>
> This is absolutely personal preference, but I prefer to have blocks have<br>
> similar syntax as methods, because that makes it easier to read code.<br>
> This means that the first line, which contains the opening bracket and the argument names, is far less important than what the block does, so it's perfectly okay to leave it on the previous line.<br>
<br>
</span>So I think you mean<br>
coll do: [:each|<br>
statement.<br>
argument.<br>
resolution].<br>
… which is pretty much how I prefer things.<br></blockquote><div><br></div><div>No. That puts the start of the block to the right of the first line of the block. That's not rectangular at all. i.e. "statement" is to the left of "[:each|". It should be</div><br> coll do:</div><div class="gmail_quote"> [:each|<br> statement.<br> argument.<br> resolution].</div><div class="gmail_quote"><br></div><div class="gmail_quote">Here, all the text of the block is included in the recangle formed by "[:each|" and "resolution]".</div><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
We should be very careful about discussing this. I don’t think anything causes more annoyance, hard feeling, lost friendships, broken communities, lost projects and global war than syntactic debates.<br></blockquote><div><br></div><div>Understood. Bt Kent gives v good rationale for all elements of his style guide, and one way of avoiding conflicts over formatting is to have and observe as much as possible, and support with tools, a house style.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span class=""><br>
tim<br>
--<br>
tim Rowledge; <a href="mailto:tim@rowledge.org">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" rel="noreferrer" target="_blank">http://www.rowledge.org/tim</a><br>
</span>Strange OpCodes: IO: Illogical Or<br>
<br>
<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><span style="font-size:small;border-collapse:separate"><div>_,,,^..^,,,_<br></div><div>best, Eliot</div></span></div></div></div>
</div></div>