Comment #1 on issue 2875 by erik.corry: Can generate (and parse) invalid
UTF-8
http://code.google.com/p/v8/issues/detail?id=2875
I'd be inclined not to fix this. If the input is malformed then it seems
more helpful to preserve the data than to start inserting error characters
into the data steam. The current behaviour is backwards compatible with
the way that js has always worked on malformed input and does the right
thing with matched surrogate pairs.
Note that the JSON standard is pre-UTF8 and is set in some according to
it's author.
Did your back end really crash or did it just throw an uncaught exception?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
