Re: [go-nuts] Re: Is encoding/json POSIX compatible?

More generally, the input and output of encoding/json need not be a file at all. On Tuesday, January 30, 2024 at 10:54:57 AM UTC-5 Brian Candler wrote: > By the definition of "3.403 Text File > " > > then

Re: [go-nuts] Re: Is encoding/json POSIX compatible?

By the definition of "3.403 Text File " then no, because a JSON file can have arbitrarily long lines. Note also: "Although POSIX.1-2017 does not distinguish between text files and binary files (see the ISO C

Re: [go-nuts] Re: Is encoding/json POSIX compatible?

So, as per the link that I sent, a json file is not a text file, right? is just a file, I want to have this clear thanks On Tue, Jan 30, 2024 at 3:50 PM 'Brian Candler' via golang-nuts < golang-nuts@googlegroups.com> wrote: > The JSON spec does not require any whitespace after the object,