aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobert Griesemer <gri@golang.org>2010-11-04 13:48:32 -0700
committerRobert Griesemer <gri@golang.org>2010-11-04 13:48:32 -0700
commitd73d1c5f324538a3186cf25d2e821901de2f0d55 (patch)
tree8167557d23de78aa6af3a96fc19cd48ae5b2469a
parent23c41a1ef2157da8df646a78f93d9b6e39a85a87 (diff)
downloadgo-d73d1c5f324538a3186cf25d2e821901de2f0d55.tar.gz
go-d73d1c5f324538a3186cf25d2e821901de2f0d55.zip
go spec: line comments may end in EOF
Consistency argument: A valid Go program should remain valid after stripping leading and trailing whitespace. This was not true so far if the last text in the source was a line comment. R=iant, ken2, r, rsc, r2 CC=golang-dev https://golang.org/cl/2906041
-rw-r--r--doc/go_spec.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/go_spec.html b/doc/go_spec.html
index cc01e433b1..e3346b271d 100644
--- a/doc/go_spec.html
+++ b/doc/go_spec.html
@@ -1,5 +1,5 @@
<!-- title The Go Programming Language Specification -->
-<!-- subtitle Version of Oct 29, 2010 -->
+<!-- subtitle Version of Nov 4, 2010 -->
<!--
TODO
@@ -138,7 +138,7 @@ There are two forms of comments:
<ol>
<li>
<i>Line comments</i> start with the character sequence <code>//</code>
-and continue through the next newline. A line comment acts like a newline.
+and stop at the end of the line. A line comment acts like a newline.
</li>
<li>
<i>General comments</i> start with the character sequence <code>/*</code>