Fwd: Hash style comments

Trans <[email protected]>
Newsgroups gmane.text.yaml.general
Message-ID <CAEu+kw24922CfdWO+FUvccPt2b65cE1eFdMEi_Jwo0WLE6n1-A@mail.gmail.com>
---------- Forwarded message ----------
From: Brendan Eich <[email protected]>
Date: Wed, Aug 8, 2012 at 2:17 PM
Subject: Re: Hash style comments
To: Russell Leggett <[email protected]>
Cc: [email protected]


Pedantry alert: someone noticed that JSON does not treat U+2028 and
U+2029 (line terminators in JS) as space characters. So these can
occur (unescaped) in JSON string literals, but not in JS string
literals. Therefore JSON accepts sentences not legal in JS:

js> JSON.parse('{"a":"\u2028","b":2}')
({a:"\u2028", b:2})
js> eval('({"a":"\u2028","b":2})')
typein:11: SyntaxError: unterminated string literal:
typein:11: ({"a":"(
typein:11: ......^

Does YAML treat U+2028 and U+2029 the same as JSON does, or as JS does?

/be

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.