Re: [Json] On characters and code points

[Tim Bray <[e-mail]>]

On Fri, Jun 7, 2013 at 9:15 AM, Stefan Drees <[e-mail]> wrote:

> and what about { "Decorate my slash": "\/" } and "general-purpose string
> processing software". Isn't this also a case, where you need a
> "pre-conditioner" that replaces the JSON specific escape sequence "\" with
> "/" before feeding it into "general-purpose string processing software" :-?)


Red herring.  JSON, just like XML, has ways to encode characters that are
hard to type.  What we're arguing about is the actual content of the
payload after the parser/pre-conditioner.  -T


>
>
>
>  Also, consider the lovely consequences when unpaired surrogates start
>> showing  up in key fields and are fed to hash functions in every
>> programming language in the world, which expect to receive Unicode
>> characters.
>>   -T
>>
>>
> For today I better not imagine all these laguages and implementations
> blindly stuffing some json text transformed into their own memory
> structures ... maybe later during the weekend
>
>
>      ...
>>
>
> Stefan.
>
>
>
>