Skip to content
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

Conformance report for reference #265

Closed
miloyip opened this issue Sep 9, 2016 · 3 comments
Closed

Conformance report for reference #265

miloyip opened this issue Sep 9, 2016 · 3 comments

Comments

@miloyip
Copy link

miloyip commented Sep 9, 2016

https://github.com/miloyip/nativejson-benchmark/blob/master/sample/conformance_json-c%20(C).md

@hawicz
Copy link
Member

hawicz commented Sep 12, 2016

Many of those are behaving as intended. If you want to be picky about what it accepted, be sure to set JSON_TOKENER_STRICT when parsing.

On the other hand, json-c's number parsing looks like it needs some fixes.

@sdrsdr
Copy link
Contributor

sdrsdr commented Feb 14, 2017

Can we have JSON5 compat table? These are really handy features: trailing comas, names without quotes, single quotes. Here is the full reference: http://json5.org/

@hawicz
Copy link
Member

hawicz commented Jul 9, 2017

Feel free to add such a page to the wiki (https://github.com/json-c/json-c/wiki).

@hawicz hawicz closed this as completed Jul 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants