Re: [Json] A possible summary of the discussion so far on code points and characters

[R S <[e-mail]>]

On Sat, Jun 8, 2013 at 5:39 PM, Carsten Bormann <[e-mail]> wrote:

>
> This view is most natural to those who think JSON should be useful as an
> interchange format for the "use a JavaScript string as a vector of
> unconstrained 16-bit values" hack.
>

We should document what currently works. It's not about expressing a
preference.

> (It is not aligned with JSON's main purpose.)

I am not sure what the rationale for that statement is.

The RFC says:

"An implementation may set limits on the length and character contents of
strings."

So maybe there's once again nothing to do here.

- Rob


sayrer$ python
Python 2.7.2 (default, Jun 20 2012, 16:23:33)
[GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import json
>>> json.loads('{"End of data marker": "\uFFFF" }')
{u'End of data marker': u'\uffff'}
>>> quit()

sayrer$ node
>
(^C again to quit)
>

sayrer$ node --version
v0.8.14

sayrer$ node
> JSON.parse('{"End of data marker": "\uFFFF" }')
{ 'End of data marker': '￿' }
> process.exit()