json-c VS JSMN

When you say .jsonc, do you mean JSONC, JSONC, or JSONC? And have I mentioned JSON-C?

to manipulate JSON data: https://github.com/json-c/json-c (I haven't used that one personally but it looks good)

If you want a comfortable developer experience without having to "develop standard functionality," choose another language.

Otherwise: libcurl for the requests, json-c[0] for the JSON handling. SDL for window handling/events/other glue stuff. I don't know what rocksdb is but I assume it has its own C API library.

[0]https://github.com/json-c/json-c

There’s also json-c and Hjson.

Yes. This library does basically that: https://github.com/json-c/json-c

$ git clone https://github.com/json-c/json-c.git $ mkdir json-c-build $ cd json-c-build $ cmake ../json-c

Look for the instructions here: https://github.com/json-c/json-c

Like how https://github.com/zserge/jsmn works. I thought it would be neat to have such as parser for https://github.com/vshymanskyy/muon

One more JSON implementation using this approach is https://github.com/zserge/jsmn.

Yep! I'm using JSMN (https://github.com/zserge/jsmn), which is a streaming parser that visits each token sequentially, so there's only one copy of each JSON response in memory. I also avoid allocating new intermediate memory whenever possible; for example, to unescape backslashes in the JSON strings, I use a destructive loop that moves the non-backslash characters forward in memory, and truncates the string by moving the null terminator earlier in the string. Not something I'd imagine doing in most environments today, but as you said, it saves a bit of space at the expense of CPU time :)

  void DestructivelyUnescapeStr(LPSTR lpInput) {

After reviewing several options, I’ve settled on plain old JSON. For parsing, I use https://github.com/zserge/jsmn. For serialization I use https://github.com/rdpoor/jems (disclaimer: I wrote the latter, but others use it as well).

As mentioned here, it appears that tiny-json is a parser, not a serializer. If you're looking for parsers, I've been very happy with jsmn.

Very small, 4-5 fields but I'm still going to write in binary because I'm trying to reduce dependencies and https://github.com/zserge/jsmn looks like good fit but jsmn only does parsing which I need for parsing some Oauth json data and config.json file. I will be able to dump the state struct in a state.bin file and read it later for comparing it with system time. Not having to write in text fits well for this particular use case. Benefits: Reduced dependencies and almost cost less decoding of the state struct(which the user will never see).

This is my very straight-forward implementation that came to be from the lack of JSON encoding in jsmn: