parson
parson copied to clipboard
kgabis
Lightweight JSON library written in C.
I missed a iterator routines, to allow people to easy walk through JSON as list keys as properties (dot) notation. It'll make things easy to get data from a file...
one of the applicatiosn of this library is on embedded systems, where functions such as fopen cannot be taken from . It'd be nice if we could leave the functions...
Example: ``` c /* Initialising object with an array of strings */ JSON_Value *val = json_value_init_object(); JSON_Object *obj = json_object(val); json_object_dotset_string(obj, "array[0]", "item0"); json_object_dotset_string(obj, "array[1]", "item1"); json_object_dotset_string(obj, "array[3]", "item3"); /*...
It seems harmless though. Found by UBSAN parson.c:270:18: runtime error: unsigned integer overflow: 0 - 1 cannot be represented in type 'size_t' (aka 'unsigned long')
Resolve conversion warnings when -Wconversion is added to the compiler arguments.
Found by clang-check. (the last one looks like a false-positive to me) parson.c:995:17: warning: Value stored to 'buf' is never read buf += written; ^ ~~~~~~~ parson.c:1016:17: warning: Value stored...
Adding a fuzzer to suggest integration with [oss-fuzz](https://github.com/google/oss-fuzz). Integrating Parson with oss-fuzz allows Google to run the fuzzer on their infrastructure continuously. The maintainers of Parson get reports via email...
Commit 96150ba removed all calls to `sscanf`, but it's still referenced in a comment here: https://github.com/kgabis/parson/blob/master/parson.c#L594 I don't know how much (if any) of this comment is still accurate. This...
I added the JSON test suite by Nicolas Seriot to the test.c. Some of the tests fail that shouldn't, which might be worth further investigation.
Will parson get stearm api for reading very large json file in the future?
