-
Notifications
You must be signed in to change notification settings - Fork 771
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected leniency with JSMN_STRICT defined #178
Comments
That's due to how primitives are currently handled by JSMN. Only the first character is checked and if it matches t, f or n it is assumed those are respectively true, false or null |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I parse a JSON
[ thanx ]
withJSMN_STRICT
defined, it doesn't really complain. Thoughthanx
is not a keyword and needs to be quoted:The text was updated successfully, but these errors were encountered: