Petri Lehtinen
Petri Lehtinen
As you said, the problem is that people are probably already working around this by outputting an extra newline. If this gets changed, the workaround causes them to have two...
Yeah, an extra flag would be better.
This is expected behavior. The hash function (hashlittle) has an optimization that Valgrind doesn't like. See the comment in https://github.com/akheron/jansson/blob/4c4f692bd6814e598c9aa538a3c9979cdf05d566/src/lookup3.h#L239-L247. IIRC, there's currently no way to disable the optimization using...
I feel this is a cumbersome approach to get essentially one more bit of integer precision. Maybe we should finally land on some way to handle arbitrary precision ints (and...
It’s not possible currently
Can you make a pull request?
This should be fixed by deprecating JSON_DECODE_ANY making it the default behavior.
You need to use the `JSON_ENCODE_ANY` flag with `json_dumps()` to encode a plain string. RFC 4627 (the old JSON spec) says that objects and arrays are the only valid top-level...
The `dump_indent` function that writes the indentation whitespace is here: https://github.com/akheron/jansson/blob/master/src/dump.c#L46-L69. I don't see how it could output garbage, unless the static whitespace buffer has been overwritten because of a...
Sounds good, please do!