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

Why is there no parse_object_stop in the streaming API? #104

Open
paulreimer opened this issue Nov 17, 2017 · 0 comments
Open

Why is there no parse_object_stop in the streaming API? #104

paulreimer opened this issue Nov 17, 2017 · 0 comments

Comments

@paulreimer
Copy link

There is a parse_array_start / parse_array_stop matching pair, and it was almost trivial for me to add one for parse_object_stop. So why is it missing?

In fact, it simplified one of my parsers greatly, and it also matches the API of other parsers (as well as seeming like it belongs in the API here, too?)

I hope that by adding+using it I am not missing something... or that there is a more elegant way enabled by the library, where I shouldn't need to add it.

I should also note that this library seems to be unlike others in its class (streaming, callback-based parsers such as libjson, or json-streaming-parser), where the picojson callback API has the additional parse_object_item and parse_array_item functions which re-enter the parser. It actually made things easier, but it doesn't seem like other SAX parsers, so I'm worried about what the trade-offs or corner cases might be.

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

1 participant