Re: [Json] Human JSON (Hjson)

[Christian Zangl <[e-mail]>]

On 2016-05-26 16:01, Phillip Hallam-Baker wrote:

> A superset of JSON encoding optimized for human input makes a lot of
> sense. In particular it should be possible for a single parser to read
> data in either strict JSON or JSON-x. Which is what I did with JSON-B,
> JSON-C and JSON-D.
>
> I suggest the following additions:
>
> 1) Comments
>
> 2) Use of quotes on labels is optional if the label conforms to C-like
> rules (does not start with a digit or contain white space, control or
> punctuation marks.
>
> 3) Allow trailing comas
>
> 4) Punctuation optional in situations it is not ambiguous.

You still have a problem with the backslash in strings. On Windows you 
can't just copy&paste a path because all \ need to be escaped. Also 
config files sometimes contain regular expressions and having to escape 
the \ makes them unreadable.

That's why Hjson has quoteless strings that are raw strings ending at LF.