From 488350ac423094a3cd252696c8e841168f1705a8 Mon Sep 17 00:00:00 2001 From: Rob Pike Date: Fri, 7 Sep 2012 10:28:24 -0700 Subject: [PATCH] spec: an initial BOM can be ignored After further deliberation, let's back down to the Unicode proposal. Ignoring aBOMinations anywhere means that things like grep unsafe *.go might fail because there's a BOM in the middle: unBOMsafe. R=golang-dev, rsc, 0xjnml, gri, bradfitz CC=golang-dev https://golang.org/cl/6490091 --- doc/go_spec.html | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/doc/go_spec.html b/doc/go_spec.html index 195f7a3c244..d10036d26a3 100644 --- a/doc/go_spec.html +++ b/doc/go_spec.html @@ -1,6 +1,6 @@ @@ -101,9 +101,8 @@ compiler may disallow the NUL character (U+0000) in the source text.

Implementation restriction: For compatibility with other tools, a -compiler may ignore any UTF-8-encoded Unicode byte order mark -(U+FEFF) in the source text outside of string -and rune literals. +compiler may ignore a UTF-8-encoded byte order mark +(U+FEFF) if it is the first Unicode code point in the source text.

Characters