On 2/19/07, <b class="gmail_sendername">Ross Paterson</b> <<a href="mailto:ross@soi.city.ac.uk">ross@soi.city.ac.uk</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, Feb 19, 2007 at 11:16:03AM +0000, Malcolm Wallace wrote:<br>> isaac jones <<a href="mailto:ijones@galois.com">ijones@galois.com</a>> wrote:<br>> > Iavor and I just made the trivial modification for DoAndIfThenElse
<br>> ><br>> > Any comments on this modification? How do people feel about the<br>> > suggestion that we do it for case statements as well?<br>><br>> I'm happy to allow the change for if-then-else. The need for extra
<br>> indentation there has annoyed me a few times.<br><br>The semicolon before the "else" is the most useful. Adding another<br>before the "then" has less motivation.</blockquote><div><br>I think it is a bad idea to make the non-layout syntax more complicated and less readable, just so that, indirectly, the layout syntax can be improved. Improvements to the layout mechanism should be localized to the section of the report describing layout, and such improvements shouldn't do anything to harm the non-layout syntax. In particular, why you don't just say that "else" and "of" act like ";" during layout?
<br><br><span style="font-family: courier new,monospace;">do { q <- if x</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> ; then y ; else z<br> ; return q<br>
}<br><br>- Brian<br><br></span></div></div>