parson

I found this while making a collection of what C implementation does what at https://news.ycombinator.com/item?id=26298300 . There are two basic implementation strategies. The BSD (FreeBSD and OpenBSD and more than likely NetBSD too), Microsoft, GNU, and MUSL C libraries use one, and suffer from this; whereas the OpenWatcom, P.J. Plauger, Tru64 Unix, and my standard C libraries use another, and do not. The 2002 report in the comp.lang.c Usenet newsgroup (listed in that discussion) is the earliest that I've found so far. There have been several assertions that library support for strings in C++ is poor. However, note that the fix here was to switch from the Standard C library function sscanf() to a C++ library. * https://github.com/fastfloat One might advocate using other people's libraries, on the grounds that they will have got such th

A JSON library in C: https://github.com/kgabis/parson

1345 days ago I posted about a C JSON library I wrote [0]. Since then I've added lots of features (serialization), fixed even more bugs (often found by someone else) and learned to say no to pull requests. It became surprisingly popular and I'm still maintaining it, adding features and fixing bugs from time to time. It feels great to know that people are using a tool you wrote and I've learned a lot about writing robust code and designing APIs thanks to it. It also helped me get my current job, so I've also benefited financially from it. Here's a direct link to github: https://github.com/kgabis/parson [0] https://news.ycombinator.com/item?id=4709169

Shameless plug: https://github.com/kgabis/parson (2-file (.h and .c) json parser)

This adds too little and too late (not that much should be added to JSON). And parsing some of these features would be a headache and a possible source of bugs (I maintain a JSON parser in C[0]). Keeping it simple is much more important than adding new features. [0] https://github.com/kgabis/parson

Well, here we go: https://github.com/kgabis/parson/issues/7

Realloc, strdup and strndup errors are handled as of now :) (https://github.com/kgabis/parson/commit/ee9be98974b3fdac0be1...) And yes, I've written my own strndup because it's "relatively new".

you are calling realloc and assigning the value directly before checking the return value. realloc can fail and return NULL and you'll overwrite the previous pointer which will cause a memory leak. I don't see why you duplicated strndup in parson_strndup. https://github.com/kgabis/parson/blob/master/parson.c#L129 parson_strdup can return NULL and this statement will fail silently.