code review 6490091: spec: BOMs can be ignored everywhere

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, 2012-09-07 16:10:52]

Hello golang-dev@googlegroups.com,

I'd like you to review this change to
https://code.google.com/p/go

[rsc, 2012-09-07 16:22:46]

It bothers me that 'grep unsafe *.go' might fail because it has been
written un<BOM>safe. Maybe we should pull back to what Unicode
suggests: BOM at beginning of file is okay, and then anywhere else is
an error.

The argument for allowing it in other places was file concatenation,
but Go programs in general are not concatenatable (cannot duplicate
the package clause) so I'm not sure this is very likely. If that came
up we could expand to 'beginning of line' instead of 'beginning of
file', but again I don't think it will.

Russ

[0xjnml, 2012-09-07 16:27:25]

I'm with Russ on this one.

-j

[r, 2012-09-07 16:33:11]

We're about to visit the last unvisited point in the design space for
these little fuckers, pardon my surrogates.

Any other votes?

-rob

[gri, 2012-09-07 16:40:48]

On 2012/09/07 16:33:11, r wrote:
> We're about to visit the last unvisited point in the design space for
> these little fuckers, pardon my surrogates.
> 
> Any other votes?
> 
> -rob

I'm ok with BOMs BOMbing anywhere but the file start. No surprises.
- gri

[bradfitz, 2012-09-07 16:41:12]

Only because you're soliciting votes:

I also think BOM only at beginning of file or line boundary.  The grep
"unsafe" argument is compelling.  Windows notepad.exe users don't cat two
files together anyway, so beginning seems fine for now.

On Fri, Sep 7, 2012 at 9:33 AM, Rob Pike <r@golang.org> wrote:

> We're about to visit the last unvisited point in the design space for
> these little fuckers, pardon my surrogates.
>
> Any other votes?
>
> -rob
>

[r, 2012-09-07 16:50:02]

It's the "for now" part that bugs me. I'd prefer "forever".

-rob

[r, 2012-09-07 17:08:31]

Hello golang-dev@googlegroups.com, rsc@golang.org, 0xjnml@gmail.com,
gri@golang.org, bradfitz@golang.org (cc: golang-dev@googlegroups.com),

Please take another look.

[0xjnml, 2012-09-07 17:14:18]

Works for me, AFAICS.

-j

[gri, 2012-09-07 17:24:59]

LGTM

[rsc, 2012-09-07 17:26:45]

LGTM but update the description.

[remyoudompheng, 2012-09-07 17:28:02]

LGTM

[r, 2012-09-07 17:28:27]

*** Submitted as http://code.google.com/p/go/source/detail?r=6887692cc272 ***

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