Nikolai Kondrashov

> and it's new and separate functionality, not affecting anything else Ah, scratch that, of course. Still, how about testing it by feeding the parser for the start?

> I don't have a problem with having some functions that are only used in tests, seeing as they should be simple functions that just wrap the functionality that's already...

Pushed #50 as the base for this one!

Rebased, ready for review :)!

Ah, rebased again on the latest "comment" commit. Ready for review! @mwilliamson, I still need this merged to complete the stream parsing feature.

> So the use case here is streaming text in, and getting a stream of JSON values out? I'd have imagined that an existing library would support the use case,...

> File objects don't necessarily need to be actual files on disk: for instance, sockets can be made into file objects using makefile(). Sure, you can wrap socket fds into...

Oh, and if we want for the program interface to use the parser interface underneath, it will have to communicate via a file. Or we'll have to have two separate...

I amended this PR to illustrate my proposal. Now it adds two functions: `jq.parse_json()` and `jq.parse_json_file()`. The implementation of the latter is trivial (but at the same time similar to...

Hi Michael, it's been a while since we discussed this PR. Would you care to take a look again? I would love to have the parser support in your repo,...