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

Update compliancy to current RFC7159 #90

Closed
1 task done
pah opened this issue Jul 30, 2014 · 3 comments
Closed
1 task done

Update compliancy to current RFC7159 #90

pah opened this issue Jul 30, 2014 · 3 comments
Assignees
Milestone

Comments

@pah
Copy link
Contributor

pah commented Jul 30, 2014

RapidJSON currently implements RFC4627, which has been superseeded by RFC7159 in March 2014.

Among mostly editorial changes, the most important update is:

RapidJSON seems to be compliant with the other changes already, AFAICS.

If you want to keep strict RFC4627-compliancy available, we could add a RAPIDJSON_RFC4627 macro to enforce the object/array top-level requirement. An AcceptAnyRoot API as proposed by #21 is then no longer needed.

@miloyip
Copy link
Collaborator

miloyip commented Jul 30, 2014

Sounds good. That simplifies many things.
I will work on it.

@pah
Copy link
Contributor Author

pah commented Jul 30, 2014

Great, thanks. The places affected can be seen in #21, which I will close now.

@miloyip
Copy link
Collaborator

miloyip commented Jul 31, 2014

I think macro is not really needed.
User can easily check the type of document after parsing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants