>
> > I need to do more testing before creating RFC for replacing the current
> > parser. There is still space for further improvements. If anyone has any
> > ideas, please let me know. Or if you could test it, that would be great
> > too! ;)
>
> At least for the decoding part, it might be worth to look at the
> "Improving JSON" proposal (http://bolinfest.com/essays/json.html).
> tl;dr: support trailing or automatic line-end commas, //-style
> comments and keys not wrapped in "s, basically extend JSON syntax to
> ES5.
>
I also oppose these proposals.
> Also, will end-users be able to get the JSON parser error message?
> Currently, all you get is a NULL returned when you have a parse error
> somewhere in your JSON - and it's a nightmare to debug with this.
>
This is a problem, I agree.