Issue 8649043: code review 8649043: spec: add another sentence about BOMs

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Issue 8649043: code review 8649043: spec: add another sentence about BOMs (Closed)

Can't Edit
Can't Publish+Mail
Start Review

Created:
11 years ago by r

Modified:
11 years ago

Reviewers:

CC:
golang-dev, dsymonds, gri

Visibility:
Public.

Description

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.

Patch Set 1 #

Patch Set 2 : diff -r b3017cc3e17b https://code.google.com/p/go/ #

Created: 11 years ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+2 lines, -1 line)			Patch
	M	doc/go_spec.html	View		2 chunks	+2 lines, -1 line	0 comments	Download

Messages

Total messages: 4

Expand All Messages | Collapse All Messages

Hello golang-dev@googlegroups.com, I'd like you to review this change to https://code.google.com/p/go/

11 years ago (2013-04-11 02:30:35 UTC) #1

11 years ago (2013-04-11 18:33:34 UTC) #4

*** Submitted as https://code.google.com/p/go/source/detail?r=b3399da3d34a ***

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://codereview.appspot.com/8649043

Expand All Messages | Collapse All Messages