README.md
1# cJSON
2
3Ultralightweight JSON parser in ANSI C.
4
5## Table of contents
6* [License](#license)
7* [Usage](#usage)
8 * [Welcome to cJSON](#welcome-to-cjson)
9 * [Building](#building)
10 * [Copying the source](#copying-the-source)
11 * [CMake](#cmake)
12 * [Makefile](#makefile)
13 * [Meson](#meson)
14 * [Vcpkg](#Vcpkg)
15 * [Including cJSON](#including-cjson)
16 * [Data Structure](#data-structure)
17 * [Working with the data structure](#working-with-the-data-structure)
18 * [Basic types](#basic-types)
19 * [Arrays](#arrays)
20 * [Objects](#objects)
21 * [Parsing JSON](#parsing-json)
22 * [Printing JSON](#printing-json)
23 * [Example](#example)
24 * [Printing](#printing)
25 * [Parsing](#parsing)
26 * [Caveats](#caveats)
27 * [Zero Character](#zero-character)
28 * [Character Encoding](#character-encoding)
29 * [C Standard](#c-standard)
30 * [Floating Point Numbers](#floating-point-numbers)
31 * [Deep Nesting Of Arrays And Objects](#deep-nesting-of-arrays-and-objects)
32 * [Thread Safety](#thread-safety)
33 * [Case Sensitivity](#case-sensitivity)
34 * [Duplicate Object Members](#duplicate-object-members)
35 * [Enjoy cJSON!](#enjoy-cjson)
36
37## License
38
39MIT License
40
41> Copyright (c) 2009-2017 Dave Gamble and cJSON contributors
42>
43> Permission is hereby granted, free of charge, to any person obtaining a copy
44> of this software and associated documentation files (the "Software"), to deal
45> in the Software without restriction, including without limitation the rights
46> to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
47> copies of the Software, and to permit persons to whom the Software is
48> furnished to do so, subject to the following conditions:
49>
50> The above copyright notice and this permission notice shall be included in
51> all copies or substantial portions of the Software.
52>
53> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
54> IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
55> FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
56> AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
57> LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
58> OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
59> THE SOFTWARE.
60
61## Usage
62
63### Welcome to cJSON.
64
65cJSON aims to be the dumbest possible parser that you can get your job done with.
66It's a single file of C, and a single header file.
67
68JSON is described best here: http://www.json.org/
69It's like XML, but fat-free. You use it to move data around, store things, or just
70generally represent your program's state.
71
72As a library, cJSON exists to take away as much legwork as it can, but not get in your way.
73As a point of pragmatism (i.e. ignoring the truth), I'm going to say that you can use it
74in one of two modes: Auto and Manual. Let's have a quick run-through.
75
76I lifted some JSON from this page: http://www.json.org/fatfree.html
77That page inspired me to write cJSON, which is a parser that tries to share the same
78philosophy as JSON itself. Simple, dumb, out of the way.
79
80### Building
81
82There are several ways to incorporate cJSON into your project.
83
84#### copying the source
85
86Because the entire library is only one C file and one header file, you can just copy `cJSON.h` and `cJSON.c` to your projects source and start using it.
87
88cJSON is written in ANSI C (C89) in order to support as many platforms and compilers as possible.
89
90#### CMake
91
92With CMake, cJSON supports a full blown build system. This way you get the most features. CMake with an equal or higher version than 2.8.5 is supported. With CMake it is recommended to do an out of tree build, meaning the compiled files are put in a directory separate from the source files. So in order to build cJSON with CMake on a Unix platform, make a `build` directory and run CMake inside it.
93
94```
95mkdir build
96cd build
97cmake ..
98```
99
100This will create a Makefile and a bunch of other files. You can then compile it:
101
102```
103make
104```
105
106And install it with `make install` if you want. By default it installs the headers `/usr/local/include/cjson` and the libraries to `/usr/local/lib`. It also installs files for pkg-config to make it easier to detect and use an existing installation of CMake. And it installs CMake config files, that can be used by other CMake based projects to discover the library.
107
108You can change the build process with a list of different options that you can pass to CMake. Turn them on with `On` and off with `Off`:
109
110* `-DENABLE_CJSON_TEST=On`: Enable building the tests. (on by default)
111* `-DENABLE_CJSON_UTILS=On`: Enable building cJSON_Utils. (off by default)
112* `-DENABLE_TARGET_EXPORT=On`: Enable the export of CMake targets. Turn off if it makes problems. (on by default)
113* `-DENABLE_CUSTOM_COMPILER_FLAGS=On`: Enable custom compiler flags (currently for Clang, GCC and MSVC). Turn off if it makes problems. (on by default)
114* `-DENABLE_VALGRIND=On`: Run tests with [valgrind](http://valgrind.org). (off by default)
115* `-DENABLE_SANITIZERS=On`: Compile cJSON with [AddressSanitizer](https://github.com/google/sanitizers/wiki/AddressSanitizer) and [UndefinedBehaviorSanitizer](https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html) enabled (if possible). (off by default)
116* `-DENABLE_SAFE_STACK`: Enable the [SafeStack](https://clang.llvm.org/docs/SafeStack.html) instrumentation pass. Currently only works with the Clang compiler. (off by default)
117* `-DBUILD_SHARED_LIBS=On`: Build the shared libraries. (on by default)
118* `-DBUILD_SHARED_AND_STATIC_LIBS=On`: Build both shared and static libraries. (off by default)
119* `-DCMAKE_INSTALL_PREFIX=/usr`: Set a prefix for the installation.
120* `-DENABLE_LOCALES=On`: Enable the usage of localeconv method. ( on by default )
121* `-DCJSON_OVERRIDE_BUILD_SHARED_LIBS=On`: Enable overriding the value of `BUILD_SHARED_LIBS` with `-DCJSON_BUILD_SHARED_LIBS`.
122* `-DENABLE_CJSON_VERSION_SO`: Enable cJSON so version. ( on by default )
123* `-DENABLE_INT64`: Enable int64 support for cjson. Please note this will use c99 instead of c89. (off by default)
124
125If you are packaging cJSON for a distribution of Linux, you would probably take these steps for example:
126```
127mkdir build
128cd build
129cmake .. -DENABLE_CJSON_UTILS=On -DENABLE_CJSON_TEST=Off -DCMAKE_INSTALL_PREFIX=/usr
130make
131make DESTDIR=$pkgdir install
132```
133
134On Windows CMake is usually used to create a Visual Studio solution file by running it inside the Developer Command Prompt for Visual Studio, for exact steps follow the official documentation from CMake and Microsoft and use the online search engine of your choice. The descriptions of the the options above still generally apply, although not all of them work on Windows.
135
136#### Makefile
137
138**NOTE:** This Method is deprecated. Use CMake if at all possible. Makefile support is limited to fixing bugs.
139
140If you don't have CMake available, but still have GNU make. You can use the makefile to build cJSON:
141
142Run this command in the directory with the source code and it will automatically compile static and shared libraries and a little test program (not the full test suite).
143
144```
145make all
146```
147
148If you want, you can install the compiled library to your system using `make install`. By default it will install the headers in `/usr/local/include/cjson` and the libraries in `/usr/local/lib`. But you can change this behavior by setting the `PREFIX` and `DESTDIR` variables: `make PREFIX=/usr DESTDIR=temp install`. And uninstall them with: `make PREFIX=/usr DESTDIR=temp uninstall`.
149
150#### Meson
151
152To make cjson work in a project using meson, the libcjson dependency has to be included:
153
154```meson
155project('c-json-example', 'c')
156
157cjson = dependency('libcjson')
158
159example = executable(
160 'example',
161 'example.c',
162 dependencies: [cjson],
163)
164```
165
166
167#### Vcpkg
168
169You can download and install cJSON using the [vcpkg](https://github.com/Microsoft/vcpkg) dependency manager:
170```
171git clone https://github.com/Microsoft/vcpkg.git
172cd vcpkg
173./bootstrap-vcpkg.sh
174./vcpkg integrate install
175vcpkg install cjson
176```
177
178The cJSON port in vcpkg is kept up to date by Microsoft team members and community contributors. If the version is out of date, please [create an issue or pull request](https://github.com/Microsoft/vcpkg) on the vcpkg repository.
179
180### Including cJSON
181
182If you installed it via CMake or the Makefile, you can include cJSON like this:
183
184```c
185#include <cjson/cJSON.h>
186```
187
188### Data Structure
189
190cJSON represents JSON data using the `cJSON` struct data type:
191
192```c
193/* The cJSON structure: */
194typedef struct cJSON
195{
196 struct cJSON *next;
197 struct cJSON *prev;
198 struct cJSON *child;
199 int type;
200 char *valuestring;
201 /* writing to valueint is DEPRECATED, use cJSON_SetNumberValue instead */
202 int valueint;
203 double valuedouble;
204 char *string;
205} cJSON;
206```
207
208An item of this type represents a JSON value. The type is stored in `type` as a bit-flag (**this means that you cannot find out the type by just comparing the value of `type`**).
209
210To check the type of an item, use the corresponding `cJSON_Is...` function. It does a `NULL` check followed by a type check and returns a boolean value if the item is of this type.
211
212The type can be one of the following:
213
214* `cJSON_Invalid` (check with `cJSON_IsInvalid`): Represents an invalid item that doesn't contain any value. You automatically have this type if you set the item to all zero bytes.
215* `cJSON_False` (check with `cJSON_IsFalse`): Represents a `false` boolean value. You can also check for boolean values in general with `cJSON_IsBool`.
216* `cJSON_True` (check with `cJSON_IsTrue`): Represents a `true` boolean value. You can also check for boolean values in general with `cJSON_IsBool`.
217* `cJSON_NULL` (check with `cJSON_IsNull`): Represents a `null` value.
218* `cJSON_Number` (check with `cJSON_IsNumber`): Represents a number value. The value is stored as a double in `valuedouble` and also in `valueint`. If the number is outside of the range of an integer, `INT_MAX` or `INT_MIN` are used for `valueint`.
219* `cJSON_String` (check with `cJSON_IsString`): Represents a string value. It is stored in the form of a zero terminated string in `valuestring`.
220* `cJSON_Array` (check with `cJSON_IsArray`): Represent an array value. This is implemented by pointing `child` to a linked list of `cJSON` items that represent the values in the array. The elements are linked together using `next` and `prev`, where the first element has `prev.next == NULL` and the last element `next == NULL`.
221* `cJSON_Object` (check with `cJSON_IsObject`): Represents an object value. Objects are stored same way as an array, the only difference is that the items in the object store their keys in `string`.
222* `cJSON_Raw` (check with `cJSON_IsRaw`): Represents any kind of JSON that is stored as a zero terminated array of characters in `valuestring`. This can be used, for example, to avoid printing the same static JSON over and over again to save performance. cJSON will never create this type when parsing. Also note that cJSON doesn't check if it is valid JSON.
223
224Additionally there are the following two flags:
225
226* `cJSON_IsReference`: Specifies that the item that `child` points to and/or `valuestring` is not owned by this item, it is only a reference. So `cJSON_Delete` and other functions will only deallocate this item, not its `child`/`valuestring`.
227* `cJSON_StringIsConst`: This means that `string` points to a constant string. This means that `cJSON_Delete` and other functions will not try to deallocate `string`.
228
229### Working with the data structure
230
231For every value type there is a `cJSON_Create...` function that can be used to create an item of that type.
232All of these will allocate a `cJSON` struct that can later be deleted with `cJSON_Delete`.
233Note that you have to delete them at some point, otherwise you will get a memory leak.
234**Important**: If you have added an item to an array or an object already, you **mustn't** delete it with `cJSON_Delete`. Adding it to an array or object transfers its ownership so that when that array or object is deleted,
235it gets deleted as well. You also could use `cJSON_SetValuestring` to change a `cJSON_String`'s `valuestring`, and you needn't to free the previous `valuestring` manually.
236
237#### Basic types
238
239* **null** is created with `cJSON_CreateNull`
240* **booleans** are created with `cJSON_CreateTrue`, `cJSON_CreateFalse` or `cJSON_CreateBool`
241* **numbers** are created with `cJSON_CreateNumber`. This will set both `valuedouble` and `valueint`. If the number is outside of the range of an integer, `INT_MAX` or `INT_MIN` are used for `valueint`
242* **strings** are created with `cJSON_CreateString` (copies the string) or with `cJSON_CreateStringReference` (directly points to the string. This means that `valuestring` won't be deleted by `cJSON_Delete` and you are responsible for its lifetime, useful for constants)
243
244#### Arrays
245
246You can create an empty array with `cJSON_CreateArray`. `cJSON_CreateArrayReference` can be used to create an array that doesn't "own" its content, so its content doesn't get deleted by `cJSON_Delete`.
247
248To add items to an array, use `cJSON_AddItemToArray` to append items to the end.
249Using `cJSON_AddItemReferenceToArray` an element can be added as a reference to another item, array or string. This means that `cJSON_Delete` will not delete that items `child` or `valuestring` properties, so no double frees are occurring if they are already used elsewhere.
250To insert items in the middle, use `cJSON_InsertItemInArray`. It will insert an item at the given 0 based index and shift all the existing items to the right.
251
252If you want to take an item out of an array at a given index and continue using it, use `cJSON_DetachItemFromArray`, it will return the detached item, so be sure to assign it to a pointer, otherwise you will have a memory leak.
253
254Deleting items is done with `cJSON_DeleteItemFromArray`. It works like `cJSON_DetachItemFromArray`, but deletes the detached item via `cJSON_Delete`.
255
256You can also replace an item in an array in place. Either with `cJSON_ReplaceItemInArray` using an index or with `cJSON_ReplaceItemViaPointer` given a pointer to an element. `cJSON_ReplaceItemViaPointer` will return `0` if it fails. What this does internally is to detach the old item, delete it and insert the new item in its place.
257
258To get the size of an array, use `cJSON_GetArraySize`. Use `cJSON_GetArrayItem` to get an element at a given index.
259
260Because an array is stored as a linked list, iterating it via index is inefficient (`O(n²)`), so you can iterate over an array using the `cJSON_ArrayForEach` macro in `O(n)` time complexity.
261
262#### Objects
263
264You can create an empty object with `cJSON_CreateObject`. `cJSON_CreateObjectReference` can be used to create an object that doesn't "own" its content, so its content doesn't get deleted by `cJSON_Delete`.
265
266To add items to an object, use `cJSON_AddItemToObject`. Use `cJSON_AddItemToObjectCS` to add an item to an object with a name that is a constant or reference (key of the item, `string` in the `cJSON` struct), so that it doesn't get freed by `cJSON_Delete`.
267Using `cJSON_AddItemReferenceToArray` an element can be added as a reference to another object, array or string. This means that `cJSON_Delete` will not delete that items `child` or `valuestring` properties, so no double frees are occurring if they are already used elsewhere.
268
269If you want to take an item out of an object, use `cJSON_DetachItemFromObjectCaseSensitive`, it will return the detached item, so be sure to assign it to a pointer, otherwise you will have a memory leak.
270
271Deleting items is done with `cJSON_DeleteItemFromObjectCaseSensitive`. It works like `cJSON_DetachItemFromObjectCaseSensitive` followed by `cJSON_Delete`.
272
273You can also replace an item in an object in place. Either with `cJSON_ReplaceItemInObjectCaseSensitive` using a key or with `cJSON_ReplaceItemViaPointer` given a pointer to an element. `cJSON_ReplaceItemViaPointer` will return `0` if it fails. What this does internally is to detach the old item, delete it and insert the new item in its place.
274
275To get the size of an object, you can use `cJSON_GetArraySize`, this works because internally objects are stored as arrays.
276
277If you want to access an item in an object, use `cJSON_GetObjectItemCaseSensitive`.
278
279To iterate over an object, you can use the `cJSON_ArrayForEach` macro the same way as for arrays.
280
281cJSON also provides convenient helper functions for quickly creating a new item and adding it to an object, like `cJSON_AddNullToObject`. They return a pointer to the new item or `NULL` if they failed.
282
283### Parsing JSON
284
285Given some JSON in a zero terminated string, you can parse it with `cJSON_Parse`.
286
287```c
288cJSON *json = cJSON_Parse(string);
289```
290
291Given some JSON in a string (whether zero terminated or not), you can parse it with `cJSON_ParseWithLength`.
292
293```c
294cJSON *json = cJSON_ParseWithLength(string, buffer_length);
295```
296
297It will parse the JSON and allocate a tree of `cJSON` items that represents it. Once it returns, you are fully responsible for deallocating it after use with `cJSON_Delete`.
298
299The allocator used by `cJSON_Parse` is `malloc` and `free` by default but can be changed (globally) with `cJSON_InitHooks`.
300
301If an error occurs a pointer to the position of the error in the input string can be accessed using `cJSON_GetErrorPtr`. Note though that this can produce race conditions in multithreading scenarios, in that case it is better to use `cJSON_ParseWithOpts` with `return_parse_end`.
302By default, characters in the input string that follow the parsed JSON will not be considered as an error.
303
304If you want more options, use `cJSON_ParseWithOpts(const char *value, const char **return_parse_end, cJSON_bool require_null_terminated)`.
305`return_parse_end` returns a pointer to the end of the JSON in the input string or the position that an error occurs at (thereby replacing `cJSON_GetErrorPtr` in a thread safe way). `require_null_terminated`, if set to `1` will make it an error if the input string contains data after the JSON.
306
307If you want more options giving buffer length, use `cJSON_ParseWithLengthOpts(const char *value, size_t buffer_length, const char **return_parse_end, cJSON_bool require_null_terminated)`.
308
309### Printing JSON
310
311Given a tree of `cJSON` items, you can print them as a string using `cJSON_Print`.
312
313```c
314char *string = cJSON_Print(json);
315```
316
317It will allocate a string and print a JSON representation of the tree into it. Once it returns, you are fully responsible for deallocating it after use with your allocator. (usually `free`, depends on what has been set with `cJSON_InitHooks`).
318
319`cJSON_Print` will print with whitespace for formatting. If you want to print without formatting, use `cJSON_PrintUnformatted`.
320
321If you have a rough idea of how big your resulting string will be, you can use `cJSON_PrintBuffered(const cJSON *item, int prebuffer, cJSON_bool fmt)`. `fmt` is a boolean to turn formatting with whitespace on and off. `prebuffer` specifies the first buffer size to use for printing. `cJSON_Print` currently uses 256 bytes for its first buffer size. Once printing runs out of space, a new buffer is allocated and the old gets copied over before printing is continued.
322
323These dynamic buffer allocations can be completely avoided by using `cJSON_PrintPreallocated(cJSON *item, char *buffer, const int length, const cJSON_bool format)`. It takes a buffer to a pointer to print to and its length. If the length is reached, printing will fail and it returns `0`. In case of success, `1` is returned. Note that you should provide 5 bytes more than is actually needed, because cJSON is not 100% accurate in estimating if the provided memory is enough.
324
325### Example
326
327In this example we want to build and parse the following JSON:
328
329```json
330{
331 "name": "Awesome 4K",
332 "resolutions": [
333 {
334 "width": 1280,
335 "height": 720
336 },
337 {
338 "width": 1920,
339 "height": 1080
340 },
341 {
342 "width": 3840,
343 "height": 2160
344 }
345 ]
346}
347```
348
349#### Printing
350
351Let's build the above JSON and print it to a string:
352
353```c
354//create a monitor with a list of supported resolutions
355//NOTE: Returns a heap allocated string, you are required to free it after use.
356char *create_monitor(void)
357{
358 const unsigned int resolution_numbers[3][2] = {
359 {1280, 720},
360 {1920, 1080},
361 {3840, 2160}
362 };
363 char *string = NULL;
364 cJSON *name = NULL;
365 cJSON *resolutions = NULL;
366 cJSON *resolution = NULL;
367 cJSON *width = NULL;
368 cJSON *height = NULL;
369 size_t index = 0;
370
371 cJSON *monitor = cJSON_CreateObject();
372 if (monitor == NULL)
373 {
374 goto end;
375 }
376
377 name = cJSON_CreateString("Awesome 4K");
378 if (name == NULL)
379 {
380 goto end;
381 }
382 /* after creation was successful, immediately add it to the monitor,
383 * thereby transferring ownership of the pointer to it */
384 cJSON_AddItemToObject(monitor, "name", name);
385
386 resolutions = cJSON_CreateArray();
387 if (resolutions == NULL)
388 {
389 goto end;
390 }
391 cJSON_AddItemToObject(monitor, "resolutions", resolutions);
392
393 for (index = 0; index < (sizeof(resolution_numbers) / (2 * sizeof(int))); ++index)
394 {
395 resolution = cJSON_CreateObject();
396 if (resolution == NULL)
397 {
398 goto end;
399 }
400 cJSON_AddItemToArray(resolutions, resolution);
401
402 width = cJSON_CreateNumber(resolution_numbers[index][0]);
403 if (width == NULL)
404 {
405 goto end;
406 }
407 cJSON_AddItemToObject(resolution, "width", width);
408
409 height = cJSON_CreateNumber(resolution_numbers[index][1]);
410 if (height == NULL)
411 {
412 goto end;
413 }
414 cJSON_AddItemToObject(resolution, "height", height);
415 }
416
417 string = cJSON_Print(monitor);
418 if (string == NULL)
419 {
420 fprintf(stderr, "Failed to print monitor.\n");
421 }
422
423end:
424 cJSON_Delete(monitor);
425 return string;
426}
427```
428
429Alternatively we can use the `cJSON_Add...ToObject` helper functions to make our lives a little easier:
430
431```c
432//NOTE: Returns a heap allocated string, you are required to free it after use.
433char *create_monitor_with_helpers(void)
434{
435 const unsigned int resolution_numbers[3][2] = {
436 {1280, 720},
437 {1920, 1080},
438 {3840, 2160}
439 };
440 char *string = NULL;
441 cJSON *resolutions = NULL;
442 size_t index = 0;
443
444 cJSON *monitor = cJSON_CreateObject();
445
446 if (cJSON_AddStringToObject(monitor, "name", "Awesome 4K") == NULL)
447 {
448 goto end;
449 }
450
451 resolutions = cJSON_AddArrayToObject(monitor, "resolutions");
452 if (resolutions == NULL)
453 {
454 goto end;
455 }
456
457 for (index = 0; index < (sizeof(resolution_numbers) / (2 * sizeof(int))); ++index)
458 {
459 cJSON *resolution = cJSON_CreateObject();
460
461 if (cJSON_AddNumberToObject(resolution, "width", resolution_numbers[index][0]) == NULL)
462 {
463 goto end;
464 }
465
466 if (cJSON_AddNumberToObject(resolution, "height", resolution_numbers[index][1]) == NULL)
467 {
468 goto end;
469 }
470
471 cJSON_AddItemToArray(resolutions, resolution);
472 }
473
474 string = cJSON_Print(monitor);
475 if (string == NULL)
476 {
477 fprintf(stderr, "Failed to print monitor.\n");
478 }
479
480end:
481 cJSON_Delete(monitor);
482 return string;
483}
484```
485
486#### Parsing
487
488In this example we will parse a JSON in the above format and check if the monitor supports a Full HD resolution while printing some diagnostic output:
489
490```c
491/* return 1 if the monitor supports full hd, 0 otherwise */
492int supports_full_hd(const char * const monitor)
493{
494 const cJSON *resolution = NULL;
495 const cJSON *resolutions = NULL;
496 const cJSON *name = NULL;
497 int status = 0;
498 cJSON *monitor_json = cJSON_Parse(monitor);
499 if (monitor_json == NULL)
500 {
501 const char *error_ptr = cJSON_GetErrorPtr();
502 if (error_ptr != NULL)
503 {
504 fprintf(stderr, "Error before: %s\n", error_ptr);
505 }
506 status = 0;
507 goto end;
508 }
509
510 name = cJSON_GetObjectItemCaseSensitive(monitor_json, "name");
511 if (cJSON_IsString(name) && (name->valuestring != NULL))
512 {
513 printf("Checking monitor \"%s\"\n", name->valuestring);
514 }
515
516 resolutions = cJSON_GetObjectItemCaseSensitive(monitor_json, "resolutions");
517 cJSON_ArrayForEach(resolution, resolutions)
518 {
519 cJSON *width = cJSON_GetObjectItemCaseSensitive(resolution, "width");
520 cJSON *height = cJSON_GetObjectItemCaseSensitive(resolution, "height");
521
522 if (!cJSON_IsNumber(width) || !cJSON_IsNumber(height))
523 {
524 status = 0;
525 goto end;
526 }
527
528 if ((width->valuedouble == 1920) && (height->valuedouble == 1080))
529 {
530 status = 1;
531 goto end;
532 }
533 }
534
535end:
536 cJSON_Delete(monitor_json);
537 return status;
538}
539```
540
541Note that there are no NULL checks except for the result of `cJSON_Parse` because `cJSON_GetObjectItemCaseSensitive` checks for `NULL` inputs already, so a `NULL` value is just propagated and `cJSON_IsNumber` and `cJSON_IsString` return `0` if the input is `NULL`.
542
543### Caveats
544
545#### Zero Character
546
547cJSON doesn't support strings that contain the zero character `'\0'` or `\u0000`. This is impossible with the current API because strings are zero terminated.
548
549#### Character Encoding
550
551cJSON only supports UTF-8 encoded input. In most cases it doesn't reject invalid UTF-8 as input though, it just propagates it through as is. As long as the input doesn't contain invalid UTF-8, the output will always be valid UTF-8.
552
553#### C Standard
554
555cJSON is written in ANSI C (or C89, C90). If your compiler or C library doesn't follow this standard, correct behavior is not guaranteed.
556
557NOTE: ANSI C is not C++ therefore it shouldn't be compiled with a C++ compiler. You can compile it with a C compiler and link it with your C++ code however. Although compiling with a C++ compiler might work, correct behavior is not guaranteed.
558
559#### Floating Point Numbers
560
561cJSON does not officially support any `double` implementations other than IEEE754 double precision floating point numbers. It might still work with other implementations but bugs with these will be considered invalid.
562
563The maximum length of a floating point literal that cJSON supports is currently 63 characters.
564
565#### Deep Nesting Of Arrays And Objects
566
567cJSON doesn't support arrays and objects that are nested too deeply because this would result in a stack overflow. To prevent this cJSON limits the depth to `CJSON_NESTING_LIMIT` which is 1000 by default but can be changed at compile time.
568
569#### Thread Safety
570
571In general cJSON is **not thread safe**.
572
573However it is thread safe under the following conditions:
574
575* `cJSON_GetErrorPtr` is never used (the `return_parse_end` parameter of `cJSON_ParseWithOpts` can be used instead)
576* `cJSON_InitHooks` is only ever called before using cJSON in any threads.
577* `setlocale` is never called before all calls to cJSON functions have returned.
578
579#### Case Sensitivity
580
581When cJSON was originally created, it didn't follow the JSON standard and didn't make a distinction between uppercase and lowercase letters. If you want the correct, standard compliant, behavior, you need to use the `CaseSensitive` functions where available.
582
583#### Duplicate Object Members
584
585cJSON supports parsing and printing JSON that contains objects that have multiple members with the same name. `cJSON_GetObjectItemCaseSensitive` however will always only return the first one.
586
587# Enjoy cJSON!
588
589- Dave Gamble (original author)
590- Max Bruckner and Alan Wang (current maintainer)
591- and the other [cJSON contributors](CONTRIBUTORS.md)
592