undefined | Better HN

0 pointseterm10y ago0 comments

But this too has significant whitespace, acting as a comma in separating properties. (It's not clear whether you can mix commas and whitespace here.)

Also this claims to not need escapes, but it's also not clear how this format handles a comma or a newline in strings without escaping, do they act as a comma to separate properties or do they act as natural commas/newlines?

0 comments

3 comments · 1 top-level

PuerkitoBio10y ago· 2 in thread

Only quoteless strings have no escapes, and according to the docs the rule is:

  > quoteless strings include everything up to the end of the
  > line, excluding trailing whitespace.

(edit: formatting)

etermOP10y ago

So this

{

  foo:one,

  bar:two

}

Parses to "one," because it is a quoteless string?

What about true and false, is false the boolean constant or a unquoted string "false".

PuerkitoBio10y ago

I posted this in another thread here, but it's documented in the linked page:

  > A value that is a number, true, false or null in JSON is parsed as a value.
  > E.g. '3' is a valid number while '3 times' is a string.

j / k navigate · click thread line to collapse