Max Bruckner

In general I would be ok with this. (better at runtime than compile time since this means that I can unit test it more easily, I've come around on that...

It can be stored as an option, the idea of #177 is to create as many configuration objects as you need and store them for later use. Then you just...

@Tangerino I don't quite understand what you mean by that. The current situation is like that: If possible, the shortest decimal representation is printed out, but in a way that...

Yeah, it might make sense to catch a `NULL` from `cJSON_strdup`, although this sadly won't enable any error handling from the external API since these are `void` functions.

Wrappers that stream to a filedescriptor could be included in the library if this is implemented.

I don't want cJSON to have a streaming interface that doesn't actually do any streaming. I'm sure there are libraries out there that implement a dynamic buffer that you can...

Yes, JSON is kind of bad for configuration files because of this. This is why I personally prefer YAML for that, although it requires a much more complex parser. I...

> As comments are not part of the JSON standard, this must be optional. This would not be enabled by default of course

Hm, seems like the testing framework I'm using doesn't completely follow ANSI C after all. For now you can fix this by not building the testing framework with `-DENABLE_CJSON_TEST=Off`

I pushed a possible fix to the `long-long-fix` branch, can you check if that fixes it?