I'm in favour of changing the comment syntax.<br><br><div><span class="gmail_quote">On 2/2/06, <b class="gmail_sendername">Manuel M T Chakravarty</b> &lt;<a href="mailto:chak@cse.unsw.edu.au">chak@cse.unsw.edu.au</a>&gt; wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I am against such a change.&nbsp;&nbsp;The change would break existing software<br>(eg, Yampa) and secondly I don't buy the &quot;main sources of
<br>confusion for beginners&quot; argument.&nbsp;&nbsp;The confusion arises only when a<br>single line comment is used to uncomment a set of characters that start<br>with a special symbol.&nbsp;&nbsp;That's a situation that doesn't arise that
<br>often.&nbsp;&nbsp;(I'd actually be very happy if the main sources of confusion fpr<br>beginners where of such simple syntactic nature.)</blockquote><div><br>Oh yes, it does happen that a single line comment begins with a special symbol. It has happened to me on several occations when using haddock annotation to my source code. It is all to easy to forget that extra space. With incomprehensible error messages as a result.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">As for consistency, well if you absolutely want to make it consistent,<br>impose the same rule on {- as on --.
</blockquote><div><br>I still think there is an inconsistency here. And it has to do with maximal munch lexing. Maximal munch is what we normally expect from a lexer for a programming language. But the way comments work at the moment breaks maximal munch. The longest possible read is to read the whole line as a comment and not interpret for instance --^ as an operator. It breaks any programmers' intuition not only beginners'. I still get it wrong from time to time.
<br><br>Cheers,<br><br>/Josef<br><br>PS. This discussion is great as a data point for Wadler's Law.</div></div>