json.Encoder adds trailing newlines. WTF?

[OpenNota]

http://play.golang.org/p/skOwJv7qZR

Any reason for this? Can this behaviour be changed by configuring the encoder? It is kind of unexpected to me. The encoding/json documentation does not mention it also.

[David Symonds]

What does it matter? It is still valid JSON, right?

[Benjamin R. Haskell]

It's not configurable, AFAICT.  From https://code.google.com/p/go/source/browse/src/pkg/encoding/json/stream.go#165

        // Terminate each value with a newline.

        // This makes the output look a little nicer

        // when debugging, and some kind of space

        // is required if the encoded value was a number,

        // so that the reader knows there aren't more

        // digits coming.

        e.WriteByte('\n')

On Sat, Apr 12, 2014 at 12:07 AM, OpenNota <open...@gmail.com> wrote:

http://play.golang.org/p/skOwJv7qZR

Any reason for this? Can this behaviour be changed by configuring the encoder? It is kind of unexpected to me. The encoding/json documentation does not mention it also.

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[OpenNota]

On Saturday, April 12, 2014 11:21:49 AM UTC+7, David Symonds wrote:

What does it matter? It is still valid JSON, right?

 I was writing unit tests for MarshalJSON, and it came as a surprise to me.

[OpenNota]

On Saturday, April 12, 2014 11:34:23 AM UTC+7, Benjamin R. Haskell wrote:

It's not configurable, AFAICT.  From https://code.google.com/p/go/source/browse/src/pkg/encoding/json/stream.go#165

        // Terminate each value with a newline.

        // This makes the output look a little nicer

        // when debugging, and some kind of space

        // is required if the encoded value was a number,

        // so that the reader knows there aren't more

        // digits coming.

        e.WriteByte('\n')

Does not the reader already knows that, because numbers will be followed by ',', '}', ']', or EOF?

[OpenNota]

I've opened an issue: http://code.google.com/p/go/issues/detail?id=7767

[OpenNota]

On Saturday, April 12, 2014 1:24:10 PM UTC+7, Islan Dberry wrote:

The decoder handles streams of JSON values. See http://godoc.org/encoding/json#example-Decoder. The decoder requires a whitespace separator between a number and the JSON value that follows it.  The encoder adds whitespace to accommodate the decoder. 

Interesting.

 

[Dan Kortschak]

The \n are not necessary for that.

http://play.golang.org/p/HVyS_WZ4xK

[OpenNota]

On Saturday, April 12, 2014 4:32:05 PM UTC+7, kortschak wrote:

The \n are not necessary for that.

I suppose they are necessary for streams of json integers.

 

[Dan Kortschak]

Yes, that's true.