Parser rejects -0 as a legitimate number. Unless I'm reading the specs wrong, a json number is:
number = [ minus ] int [ frac ] [ exp ]
and an int is:
int = zero / ( digit1-9 *DIGIT )
I'm referencing: http://www.ietf.org/rfc/rfc4627.txt
A fairly easy workaround that I'm currently using is to replace -0 with 0 and then parsing. That's working for me.
(If you need some sample json strings I'm happy to provide)
Parse -0 correctly. Fixes #88.