-0 gets rejected as a number (error: "No digits after initial minus")

[briancsinger]

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)

[stig]

Hi. Thanks for reporting this. The issue should be fixed in master. I've also released 3.0.2 with this fix.

Stig

On 27 Jul 2011, at 04:32, briancsinger wrote:

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)

Reply to this email directly or view it on GitHub:
#88