<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Jaeho Lee wrote:
<blockquote cite="mid:000001c93e55$982c6b80$c8854280$@ac.kr" type="cite">
<pre wrap="">Hello,
</pre>
</blockquote>
Hi. :-)<br>
<blockquote cite="mid:000001c93e55$982c6b80$c8854280$@ac.kr" type="cite">
<pre wrap="">I strongly support the idea of putting semicolons at the end of every
"statement" (define if needed).
</pre>
<blockquote type="cite">
<pre wrap="">Hi all,
This spring in Oslo we introduced semicolons to delimit statements
within topic blocks [1] (for no technical reason but to enhance
readability for non-SVO languages).
</pre>
</blockquote>
<pre wrap=""><!---->
I think there were other technical reasons mentioned in Oslo more than just
readability for non-SVO languages.
</pre>
</blockquote>
Can you please elaborate on this point more in-depth? More specifically:<br>
<ul>
<li><i>What specificity of East Asian languages prevents readability
of CTM documents without semicolons which is re-gained with semicolons?</i></li>
</ul>
Or even more specifically: Given the fact that most CTM documents will
have one statement per line (because this is already custom in present
CTM documents as well as other languages to have one statement per line
and presumably because it allows faster visual scanning), the new-line
character actually serves as a de-facto semicolon-character. We could
even go that far and make the new-line character serve as a de-standard
semicolon-character. So, given this:<br>
<ul>
<li><i>What specificity of East Asian languages prevents readability
of CTM documents with new-lines after every statement without
semicolons which is re-gained with semicolons before the new-lines?</i></li>
</ul>
I've been asking every person I could get hold of at the TMRA 2008 to
explain to me what the impact is for non-SVO languages (or East Asian
languages specifically) regarding semicolons. However, nobody could
explain it to me. I also asked Naito-san, and he also could not explain
it to me. He also thinks that in his opinion, semicolons are not needed
for Japanese speakers. This strikes me, as one of the most modern
programming languages (in terms of compactness and readability), namely
Ruby ( <a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/Ruby_(programming_language)">http://en.wikipedia.org/wiki/Ruby_(programming_language)</a> ), is
invented by a Japanese native speaker, and this language avoids
semicolons where it can. So, apparently, there is no consensus about
non-SVO native speakers or just East Asian languages' speakers about
the necessity of semicolons. It is clear that CTM has a SVO-centric
bias and thus maybe a Western bias (and I'm happy to help fixing that).
However, it is unclear to me why semicolons could help improve
readability for East Asian languages' speakers. That's why I'm asking
you.<br>
<br>
<br>
I'll get to your other points as soon as I get your reply. :-)<br>
<br>
ciao,<br>
Xuân.<br>
<br>
<br>
<blockquote cite="mid:000001c93e55$982c6b80$c8854280$@ac.kr" type="cite">
<pre wrap="">One of them is easiness for the parser, and more importantly easiness for
the generator of CTM statements.
My many application programs will generate CTM statements routinely, and
handling optional component is always headache.
Furthermore readability and ugliness are so subjective issues. I see the
beauty of consistent when there are always semicolons at the end of every
statement.
</pre>
</blockquote>
<br>
<br>
</body>
</html>