Is cJSON thread-safe about cjson HOT 2 CLOSED

In general: No.

But it depends on how you use it.

There are three global variables:

• global_ep: If parsing fails it contains a pointer to the position in the input string where it happened. It is automatically set by cJSON_Parse.
• cJSON_Malloc and cJSON_Free: Function pointers pointing to the allocator and deallocator that is used by cJSON. They can be set with cJSON_InitHooks.

If you don't rely on these, cJSON is thread safe. You can avoid using global_ep by parsing with cJSON_ParseWithOpts, if not NULL, it will use return_parse_end instead of global_ep.

So cJSON is thread safe under these conditions:

• Use cJSON_ParseWithOpts and pass in your own error pointer via return_parse_end
• Either don't use cJSON_InitHooks, or only do it once at the beginning, before any thread starts using the library.

With the upcoming 2.0.0 release, cJSON will be thread safe though, because the global variables will be replaced by ones that are passed in on every function call. But I can not make any guarantees as to when 2.0.0 will be ready.

from cjson.

Use cJSON_ParseWithOpts and pass in your own error pointer via return_parse_end

I don't think this is correct. At the beginning global_error.json and global_error.position are reset unconditionally and in the failure case, global_error is overwritten unconditionally.

Is there a timeline for a 2.0 release?

from cjson.