Re: [Json] JSON Log file encoding JSON-L

[Phillip Hallam-Baker <[e-mail]>]

On Wed, May 7, 2014 at 5:04 PM, Nico Williams <[e-mail]> wrote:
> On Wed, May 7, 2014 at 3:46 PM, Phillip Hallam-Baker <[e-mail]> wrote:
>> If I open up a file with an RS character in it using notepad, how is
>> it going to look?
>
> Notepad, Wordpad, my Unix shells, my Unix $EDITOR -- all display it as
> a space or not at all.

So how can I look at a file and know if it is a well formed sequence or not?


>> Since RS is effectively an obsolete character the best I would expect
>> is to see ? all over the place.
>
> Nope.  And even so, who cares?  It's a log file, you'll not be editing it.

I open log files with an editor very frequently.


>> Unix and Windows both came to the conclusion that the only control
>> characters that are used are CR, LF and TAB. And CR is only used
>> because the Internet adopted CRLF as the line ending sequence rather
>> than LF.
>
> Try it.
>
>> JSON is a text based encoding. It is not the place to attempt to
>> resurrect long abandoned control character conventions.
>
> Try it.
>
> Nico
> --

It is easy enough to detect the sequence '}' *ws* LF *ws '{', its a
four state FSR. Why complicate things with characters that will cause
detours through untested code paths?



-- 
Website: http://hallambaker.com/