From: Rob Pike Date: Thu, 11 Apr 2013 18:33:25 +0000 (-0700) Subject: spec: add another sentence about BOMs X-Git-Tag: go1.1rc2~116 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=548c65a568e14490f1a6b80e92c175e2410ddf20;p=gostls13.git spec: add another sentence about BOMs Although one may argue that they should be legal, gc (at least) disallows byte order marks that are not the first code point in the file. Added a sentence to the "Implementation restriction" clause in the "Source code representation" section to document this better. Lifting this restriction (again - the rule has changed at least twice already) would not break any existing programs, should we later decide yet again to fiddle the rules about these little fly specks. R=golang-dev, dsymonds, gri CC=golang-dev https://golang.org/cl/8649043 --- diff --git a/doc/go_spec.html b/doc/go_spec.html index 214d1c0acc..5cc452d208 100644 --- a/doc/go_spec.html +++ b/doc/go_spec.html @@ -1,6 +1,6 @@ @@ -103,6 +103,7 @@ compiler may disallow the NUL character (U+0000) in the source text. Implementation restriction: For compatibility with other tools, a compiler may ignore a UTF-8-encoded byte order mark (U+FEFF) if it is the first Unicode code point in the source text. +A byte order mark may be disallowed anywhere else in the source.

Characters