qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-12 03:10:22 -07:00
Code Releases Activity

spec: add another sentence about BOMs

Browse Source 
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
This commit is contained in:
Rob Pike 2013-04-11 11:33:25 -07:00
parent d06be395cc
commit 548c65a568
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/go_spec.html
View File

@ -1,6 +1,6 @@
<!--{
"Title": "The Go Programming Language Specification",
"Subtitle": "Version of April 3, 2013",
"Subtitle": "Version of April 10, 2013",
"Path": "/ref/spec"
}-->
@ -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.
</p>
<h3 id="Characters">Characters</h3>