All declarations are in jansson.h, so it’s enough to
#include <jansson.h>
in each source file.
All constants are prefixed with JSON_ (except for those describing the library version, prefixed with JANSSON_). Other identifiers are prefixed with json_. Type names are suffixed with _t and typedef‘d so that the struct keyword need not be used.
The Jansson version is of the form A.B.C, where A is the major version, B is the minor version and C is the micro version. If the micro version is zero, it’s omitted from the version string, i.e. the version string is just A.B.
When a new release only fixes bugs and doesn’t add new features or functionality, the micro version is incremented. When new features are added in a backwards compatible way, the minor version is incremented and the micro version is set to zero. When there are backwards incompatible changes, the major version is incremented and others are set to zero.
The following preprocessor constants specify the current version of the library:
A 3-byte hexadecimal representation of the version, e.g. 0x010201 for version 1.2.1 and 0x010300 for version 1.3. This is useful in numeric comparisons, e.g.:
#if JANSSON_VERSION_HEX >= 0x010300
/* Code specific to version 1.3 and above */
#endif
The JSON specification (RFC 4627) defines the following data types: object, array, string, number, boolean, and null. JSON types are used dynamically; arrays and objects can hold any other data type, including themselves. For this reason, Jansson’s type system is also dynamic in nature. There’s one C type to represent all JSON values, and this structure knows the type of the JSON value it holds.
Objects of :type:`json_t` are always used through a pointer. There are APIs for querying the type, manipulating the reference count, and for constructing and manipulating values of different types.
Unless noted otherwise, all API functions return an error value if an error occurs. Depending on the function’s signature, the error value is either NULL or -1. Invalid arguments or invalid input are apparent sources for errors. Memory allocation and I/O operations may also cause errors.
Alias of json_is_true(), i.e. returns 1 for JSON_TRUE and 0 otherwise.
New in version 2.7.
The reference count is used to track whether a value is still in use or not. When a value is created, it’s reference count is set to 1. If a reference to a value is kept (e.g. a value is stored somewhere for later use), its reference count is incremented, and when the value is no longer needed, the reference count is decremented. When the reference count drops to zero, there are no references left, and the value can be destroyed.
Functions creating new JSON values set the reference count to 1. These functions are said to return a new reference. Other functions returning (existing) JSON values do not normally increase the reference count. These functions are said to return a borrowed reference. So, if the user will hold a reference to a value returned as a borrowed reference, he must call json_incref(). As soon as the value is no longer needed, json_decref() should be called to release the reference.
Normally, all functions accepting a JSON value as an argument will manage the reference, i.e. increase and decrease the reference count as needed. However, some functions steal the reference, i.e. they have the same result as if the user called json_decref() on the argument right after calling the function. These functions are suffixed with _new or have _new_ somewhere in their name.
For example, the following code creates a new JSON array and appends an integer to it:
json_t *array, *integer;
array = json_array();
integer = json_integer(42);
json_array_append(array, integer);
json_decref(integer);
Note how the caller has to release the reference to the integer value by calling json_decref(). By using a reference stealing function json_array_append_new() instead of json_array_append(), the code becomes much simpler:
json_t *array = json_array();
json_array_append_new(array, json_integer(42));
In this case, the user doesn’t have to explicitly release the reference to the integer value, as json_array_append_new() steals the reference when appending the value to the array.
In the following sections it is clearly documented whether a function will return a new or borrowed reference or steal a reference to its argument.
A circular reference is created when an object or an array is, directly or indirectly, inserted inside itself. The direct case is simple:
json_t *obj = json_object();
json_object_set(obj, "foo", obj);
Jansson will refuse to do this, and json_object_set() (and all the other such functions for objects and arrays) will return with an error status. The indirect case is the dangerous one:
json_t *arr1 = json_array(), *arr2 = json_array();
json_array_append(arr1, arr2);
json_array_append(arr2, arr1);
In this example, the array arr2 is contained in the array arr1, and vice versa. Jansson cannot check for this kind of indirect circular references without a performance hit, so it’s up to the user to avoid them.
If a circular reference is created, the memory consumed by the values cannot be freed by json_decref(). The reference counts never drops to zero because the values are keeping the references to each other. Moreover, trying to encode the values with any of the encoding functions will fail. The encoder detects circular references and returns an error status.
New in version 2.9.
It is possible to use the json_auto_t type to automatically dereference a value at the end of a scope. For example:
void function(void) {
json_auto_t *value = NULL;
value = json_string("foo");
/* json_decref(value) is automatically called. */
}
This feature is only available on GCC and Clang. So if your project has a portability requirement for other compilers, you should avoid this feature.
Additionally, as always, care should be taken when passing values to functions that steal references.
These three values are implemented as singletons, so the returned pointers won’t change between invocations of these functions.
Returns the JSON true value.
Returns the JSON false value.
Returns JSON false if val is zero, and JSON true otherwise. This is a macro, and equivalent to val ? json_true() : json_false().
New in version 2.4.
Returns the JSON null value.
Jansson uses UTF-8 as the character encoding. All JSON strings must be valid UTF-8 (or ASCII, as it’s a subset of UTF-8). All Unicode codepoints U+0000 through U+10FFFF are allowed, but you must use length-aware functions if you wish to embed null bytes in strings.
Returns a new JSON string, or NULL on error. value must be a valid null terminated UTF-8 encoded Unicode string.
Like json_string(), but with explicit length, so value may contain null characters or not be null terminated.
New in version 2.7.
Like json_string(), but doesn’t check that value is valid UTF-8. Use this function only if you are certain that this really is the case (e.g. you have already checked it by other means).
Like json_string_nocheck(), but with explicit length, so value may contain null characters or not be null terminated.
New in version 2.7.
Returns the associated value of string as a null terminated UTF-8 encoded string, or NULL if string is not a JSON string.
The returned value is read-only and must not be modified or freed by the user. It is valid as long as string exists, i.e. as long as its reference count has not dropped to zero.
Returns the length of string in its UTF-8 presentation, or zero if string is not a JSON string.
New in version 2.7.
Like json_string_set(), but with explicit length, so value may contain null characters or not be null terminated.
New in version 2.7.
Like json_string_set_nocheck(), but with explicit length, so value may contain null characters or not be null terminated.
New in version 2.7.
Construct a JSON string from a format string and varargs, just like printf().
New in version 2.11.
The JSON specification only contains one numeric type, “number”. The C programming language has distinct types for integer and floating-point numbers, so for practical reasons Jansson also has distinct types for the two. They are called “integer” and “real”, respectively. For more information, see RFC Conformance.
This is a preprocessor variable that holds the value 1 if :type:`json_int_t` is long long, and 0 if it’s long. It can be used as follows:
#if JSON_INTEGER_IS_LONG_LONG
/* Code specific for long long */
#else
/* Code specific for long */
#endif
This is a macro that expands to a printf() conversion specifier that corresponds to :type:`json_int_t`, without the leading % sign, i.e. either "lld" or "ld". This macro is required because the actual type of :type:`json_int_t` can be either long or long long, and printf() requires different length modifiers for the two.
Example:
json_int_t x = 123123123;
printf("x is %" JSON_INTEGER_FORMAT "\n", x);
Returns a new JSON integer, or NULL on error.
Returns a new JSON real, or NULL on error.
A JSON array is an ordered collection of other JSON values.
Returns a new JSON array, or NULL on error. Initially, the array is empty.
Returns the element in array at position index. The valid range for index is from 0 to the return value of json_array_size() minus 1. If array is not a JSON array, if array is NULL, or if index is out of range, NULL is returned.
Iterate over every element of array, running the block of code that follows each time with the proper values set to variables index and value, of types :type:`size_t` and :type:`json_t *` respectively. Example:
/* array is a JSON array */
size_t index;
json_t *value;
json_array_foreach(array, index, value) {
/* block of code that uses index and value */
}
The items are returned in increasing index order.
This macro expands to an ordinary for statement upon preprocessing, so its performance is equivalent to that of hand-written code using the array access functions. The main advantage of this macro is that it abstracts away the complexity, and makes for more concise and readable code.
New in version 2.5.
A JSON object is a dictionary of key-value pairs, where the key is a Unicode string and the value is any JSON value.
Even though null bytes are allowed in string values, they are not allowed in object keys.
Returns a new JSON object, or NULL on error. Initially, the object is empty.
Get a value corresponding to key from object. Returns NULL if key is not found and on error.
Like json_object_update(), but only the values of existing keys are updated. No new keys are created. Returns 0 on success or -1 on error.
New in version 2.3.
Like json_object_update(), but only new keys are created. The value of any existing key is not changed. Returns 0 on success or -1 on error.
New in version 2.3.
Iterate over every key-value pair of object, running the block of code that follows each time with the proper values set to variables key and value, of types :type:`const char *` and :type:`json_t *` respectively. Example:
/* obj is a JSON object */
const char *key;
json_t *value;
json_object_foreach(obj, key, value) {
/* block of code that uses key and value */
}
The items are returned in the order they were inserted to the object.
Note: It’s not safe to call json_object_del(object, key) during iteration. If you need to, use json_object_foreach_safe() instead.
This macro expands to an ordinary for statement upon preprocessing, so its performance is equivalent to that of hand-written iteration code using the object iteration protocol (see below). The main advantage of this macro is that it abstracts away the complexity behind iteration, and makes for more concise and readable code.
New in version 2.3.
Like json_object_foreach(), but it’s safe to call json_object_del(object, key) during iteration. You need to pass an extra void * parameter tmp that is used for temporary storage.
New in version 2.8.
The following functions can be used to iterate through all key-value pairs in an object. The items are returned in the order they were inserted to the object.
Extract the associated value from iter.
Like json_object_iter_at(), but much faster. Only works for values returned by json_object_iter_key(). Using other keys will lead to segfaults. This function is used internally to implement json_object_foreach(). Example:
/* obj is a JSON object */
const char *key;
json_t *value;
void *iter = json_object_iter(obj);
while(iter)
{
key = json_object_iter_key(iter);
value = json_object_iter_value(iter);
/* use key and value ... */
iter = json_object_iter_next(obj, iter);
}
New in version 2.3.
Seed the hash function used in Jansson’s hashtable implementation. The seed is used to randomize the hash function so that an attacker cannot control its output.
If seed is 0, Jansson generates the seed itself by reading random data from the operating system’s entropy sources. If no entropy sources are available, falls back to using a combination of the current timestamp (with microsecond precision if possible) and the process ID.
If called at all, this function must be called before any calls to json_object(), either explicit or implicit. If this function is not called by the user, the first call to json_object() (either explicit or implicit) seeds the hash function. See Thread safety for notes on thread safety.
If repeatable results are required, for e.g. unit tests, the hash function can be “unrandomized” by calling json_object_seed() with a constant value on program startup, e.g. json_object_seed(1).
New in version 2.6.
Jansson uses a single struct type to pass error information to the user. See sections Decoding, Building Values and Parsing and Validating Values for functions that pass error information using this struct.
The normal use of :type:`json_error_t` is to allocate it on the stack, and pass a pointer to a function. Example:
int main() {
json_t *json;
json_error_t error;
json = json_load_file("/path/to/file.json", 0, &error);
if(!json) {
/* the error variable contains error information */
}
...
}
Also note that if the call succeeded (json != NULL in the above example), the contents of error are generally left unspecified. The decoding functions write to the position member also on success. See Decoding for more info.
All functions also accept NULL as the :type:`json_error_t` pointer, in which case no error information is returned to the caller.
Returns the error code embedded in error->text.
New in version 2.11.
This sections describes the functions that can be used to encode values to JSON. By default, only objects and arrays can be encoded directly, since they are the only valid root values of a JSON text. To encode any JSON value, use the JSON_ENCODE_ANY flag (see below).
By default, the output has no newlines, and spaces are used between array and object elements for a readable output. This behavior can be altered by using the JSON_INDENT and JSON_COMPACT flags described below. A newline is never appended to the end of the encoded JSON data.
Each function takes a flags parameter that controls some aspects of how the data is encoded. Its default value is 0. The following macros can be ORed together to obtain flags.
Pretty-print the result, using newlines between array and object items, and indenting with n spaces. The valid range for n is between 0 and 31 (inclusive), other values result in an undefined output. If JSON_INDENT is not used or n is 0, no newlines are inserted between array and object items.
The JSON_MAX_INDENT constant defines the maximum indentation that can be used, and its value is 31.
Changed in version 2.7: Added JSON_MAX_INDENT.
Deprecated since version 2.8: Order of object keys is always preserved.
Prior to version 2.8: If this flag is used, object keys in the output are sorted into the same order in which they were first inserted to the object. For example, decoding a JSON text and then encoding with this flag preserves the order of object keys.
Specifying this flag makes it possible to encode any JSON value on its own. Without it, only objects and arrays can be passed as the json value to the encoding functions.
Note: Encoding any value may be useful in some scenarios, but it’s generally discouraged as it violates strict compatibility with RFC 4627. If you use this flag, don’t expect interoperability with other JSON systems.
New in version 2.1.
Escape the / characters in strings with \/.
New in version 2.4.
Output all real numbers with at most n digits of precision. The valid range for n is between 0 and 31 (inclusive), and other values result in an undefined behavior.
By default, the precision is 17, to correctly and losslessly encode all IEEE 754 double precision floating point numbers.
New in version 2.7.
If this flag is used, the opening and closing characters of the top-level array (‘[‘, ‘]’) or object (‘{‘, ‘}’) are omitted during encoding. This flag is useful when concatenating multiple arrays or objects into a stream.
New in version 2.10.
These functions output UTF-8:
Writes the JSON representation of json to the buffer of size bytes. Returns the number of bytes that would be written or 0 on error. flags is described above. buffer is not null-terminated.
This function never writes more than size bytes. If the return value is greater than size, the contents of the buffer are undefined. This behavior enables you to specify a NULL buffer to determine the length of the encoding. For example:
size_t size = json_dumpb(json, NULL, 0, 0);
if (size == 0)
return -1;
char *buf = alloca(size);
size = json_dumpb(json, buf, size, 0);
New in version 2.10.
Write the JSON representation of json to the stream output. flags is described above. Returns 0 on success and -1 on error. If an error occurs, something may have already been written to output. In this case, the output is undefined and most likely not valid JSON.
It is important to note that this function can only succeed on stream file descriptors (such as SOCK_STREAM). Using this function on a non-stream file descriptor will result in undefined behavior. For non-stream file descriptors, see instead json_dumpb().
This function requires POSIX and fails on all non-POSIX systems.
New in version 2.10.
Call callback repeatedly, passing a chunk of the JSON representation of json each time. flags is described above. Returns 0 on success and -1 on error.
New in version 2.2.
This sections describes the functions that can be used to decode JSON text to the Jansson representation of JSON data. The JSON specification requires that a JSON text is either a serialized array or object, and this requirement is also enforced with the following functions. In other words, the top level value in the JSON text being decoded must be either array or object. To decode any JSON value, use the JSON_DECODE_ANY flag (see below).
See RFC Conformance for a discussion on Jansson’s conformance to the JSON specification. It explains many design decisions that affect especially the behavior of the decoder.
Each function takes a flags parameter that can be used to control the behavior of the decoder. Its default value is 0. The following macros can be ORed together to obtain flags.
Issue a decoding error if any JSON object in the input text contains duplicate keys. Without this flag, the value of the last occurrence of each key ends up in the result. Key equivalence is checked byte-by-byte, without special Unicode comparison algorithms.
New in version 2.1.
By default, the decoder expects an array or object as the input. With this flag enabled, the decoder accepts any valid JSON value.
Note: Decoding any value may be useful in some scenarios, but it’s generally discouraged as it violates strict compatibility with RFC 4627. If you use this flag, don’t expect interoperability with other JSON systems.
New in version 2.3.
By default, the decoder expects that its whole input constitutes a valid JSON text, and issues an error if there’s extra data after the otherwise valid JSON input. With this flag enabled, the decoder stops after decoding a valid JSON array or object, and thus allows extra data after the JSON text.
Normally, reading will stop when the last ] or } in the JSON input is encountered. If both JSON_DISABLE_EOF_CHECK and JSON_DECODE_ANY flags are used, the decoder may read one extra UTF-8 code unit (up to 4 bytes of input). For example, decoding 4true correctly decodes the integer 4, but also reads the t. For this reason, if reading multiple consecutive values that are not arrays or objects, they should be separated by at least one whitespace character.
New in version 2.1.
JSON defines only one number type. Jansson distinguishes between ints and reals. For more information see Real vs. Integer. With this flag enabled the decoder interprets all numbers as real values. Integers that do not have an exact double representation will silently result in a loss of precision. Integers that cause a double overflow will cause an error.
New in version 2.5.
Allow \u0000 escape inside string values. This is a safety measure; If you know your input can contain null bytes, use this flag. If you don’t use this flag, you don’t have to worry about null bytes inside strings unless you explicitly create themselves by using e.g. json_stringn() or s# format specifier for json_pack().
Object keys cannot have embedded null bytes even if this flag is used.
New in version 2.6.
Each function also takes an optional :type:`json_error_t` parameter that is filled with error information if decoding fails. It’s also updated on success; the number of bytes of input read is written to its position field. This is especially useful when using JSON_DISABLE_EOF_CHECK to read multiple consecutive JSON texts.
New in version 2.3: Number of bytes of input read is written to the position field of the :type:`json_error_t` structure.
If no error or position information is needed, you can pass NULL.
Decodes the JSON string input and returns the array or object it contains, or NULL on error, in which case error is filled with information about the error. flags is described above.
Decodes the JSON string buffer, whose length is buflen, and returns the array or object it contains, or NULL on error, in which case error is filled with information about the error. This is similar to json_loads() except that the string doesn’t need to be null-terminated. flags is described above.
New in version 2.1.
Decodes the JSON text in stream input and returns the array or object it contains, or NULL on error, in which case error is filled with information about the error. flags is described above.
This function will start reading the input from whatever position the input file was in, without attempting to seek first. If an error occurs, the file position will be left indeterminate. On success, the file position will be at EOF, unless JSON_DISABLE_EOF_CHECK flag was used. In this case, the file position will be at the first character after the last ] or } in the JSON input. This allows calling json_loadf() on the same FILE object multiple times, if the input consists of consecutive JSON texts, possibly separated by whitespace.
Decodes the JSON text in stream input and returns the array or object it contains, or NULL on error, in which case error is filled with information about the error. flags is described above.
This function will start reading the input from whatever position the input file descriptor was in, without attempting to seek first. If an error occurs, the file position will be left indeterminate. On success, the file position will be at EOF, unless JSON_DISABLE_EOF_CHECK flag was used. In this case, the file descriptor’s position will be at the first character after the last ] or } in the JSON input. This allows calling json_loadfd() on the same file descriptor multiple times, if the input consists of consecutive JSON texts, possibly separated by whitespace.
It is important to note that this function can only succeed on stream file descriptors (such as SOCK_STREAM). Using this function on a non-stream file descriptor will result in undefined behavior. For non-stream file descriptors, see instead json_loadb().
This function requires POSIX and fails on all non-POSIX systems.
New in version 2.10.
Decodes the JSON text in file path and returns the array or object it contains, or NULL on error, in which case error is filled with information about the error. flags is described above.
Decodes the JSON text produced by repeated calls to callback, and returns the array or object it contains, or NULL on error, in which case error is filled with information about the error. data is passed through to callback on each call. flags is described above.
New in version 2.4.
This section describes functions that help to create, or pack, complex JSON values, especially nested objects and arrays. Value building is based on a format string that is used to tell the functions about the expected arguments.
For example, the format string "i" specifies a single integer value, while the format string "[ssb]" or the equivalent "[s, s, b]" specifies an array value with two strings and a boolean as its items:
/* Create the JSON integer 42 */
json_pack("i", 42);
/* Create the JSON array ["foo", "bar", true] */
json_pack("[ssb]", "foo", "bar", 1);
Here’s the full list of format specifiers. The type in parentheses denotes the resulting JSON type, and the type in brackets (if any) denotes the C type that is expected as the corresponding argument or arguments.
Like s, but if the argument is NULL, output a JSON null value.
New in version 2.8.
Like s, but if the argument is NULL, do not output any value. This format can only be used inside an object or an array. If used inside an object, the corresponding key is additionally suppressed when the value is omitted. See below for an example.
New in version 2.11.
Convert a UTF-8 buffer of a given length to a JSON string.
New in version 2.5.
Like s# but the length argument is of type :type:`size_t`.
New in version 2.6.
Like s, but concatenate to the previous string. Only valid after s, s#, + or +#.
New in version 2.5.
Like s#, but concatenate to the previous string. Only valid after s, s#, + or +#.
New in version 2.5.
Like +# but the length argument is of type :type:`size_t`.
New in version 2.6.
Like o and O, respectively, but if the argument is NULL, output a JSON null value.
New in version 2.8.
Like o and O, respectively, but if the argument is NULL, do not output any value. This format can only be used inside an object or an array. If used inside an object, the corresponding key is additionally suppressed. See below for an example.
New in version 2.11.
Whitespace, : and , are ignored.
Build a new JSON value according to the format string fmt. For each format specifier (except for {}[]n), one or more arguments are consumed and used to build the corresponding value. Returns NULL on error.
Like json_pack(), but an in the case of an error, an error message is written to error, if it’s not NULL. The flags parameter is currently unused and should be set to 0.
As only the errors in format string (and out-of-memory errors) can be caught by the packer, these two functions are most likely only useful for debugging format strings.
More examples:
/* Build an empty JSON object */
json_pack("{}");
/* Build the JSON object {"foo": 42, "bar": 7} */
json_pack("{sisi}", "foo", 42, "bar", 7);
/* Like above, ':', ',' and whitespace are ignored */
json_pack("{s:i, s:i}", "foo", 42, "bar", 7);
/* Build the JSON array [[1, 2], {"cool": true}] */
json_pack("[[i,i],{s:b}]", 1, 2, "cool", 1);
/* Build a string from a non-null terminated buffer */
char buffer[4] = {'t', 'e', 's', 't'};
json_pack("s#", buffer, 4);
/* Concatenate strings together to build the JSON string "foobarbaz" */
json_pack("s++", "foo", "bar", "baz");
/* Create an empty object or array when optional members are missing */
json_pack("{s:s*,s:o*,s:O*}", "foo", NULL, "bar", NULL, "baz", NULL);
json_pack("[s*,o*,O*]", NULL, NULL, NULL);
This section describes functions that help to validate complex values and extract, or unpack, data from them. Like building values, this is also based on format strings.
While a JSON value is unpacked, the type specified in the format string is checked to match that of the JSON value. This is the validation part of the process. In addition to this, the unpacking functions can also check that all items of arrays and objects are unpacked. This check be enabled with the format specifier ! or by using the flag JSON_STRICT. See below for details.
Here’s the full list of format specifiers. The type in parentheses denotes the JSON type, and the type in brackets (if any) denotes the C type whose address should be passed.
Convert a JSON string to a pointer to a null terminated UTF-8 string and its length.
New in version 2.6.
Convert each item in the JSON object according to the inner format string fmt. The first, third, etc. format specifier represent a key, and must be s. The corresponding argument to unpack functions is read as the object key. The second fourth, etc. format specifier represent a value and is written to the address given as the corresponding argument. Note that every other argument is read from and every other is written to.
fmt may contain objects and arrays as values, i.e. recursive value extraction is supported.
New in version 2.3: Any s representing a key may be suffixed with a ? to make the key optional. If the key is not found, nothing is extracted. See below for an example.
Whitespace, : and , are ignored.
Note
The first argument of all unpack functions is json_t *root instead of const json_t *root, because the use of O format specifier causes the reference count of root, or some value reachable from root, to be increased. Furthermore, the o format specifier may be used to extract a value as-is, which allows modifying the structure or contents of a value reachable from root.
If the O and o format specifiers are not used, it’s perfectly safe to cast a const json_t * variable to plain json_t * when used with these functions.
The following unpacking flags are available:
Examples:
/* root is the JSON integer 42 */
int myint;
json_unpack(root, "i", &myint);
assert(myint == 42);
/* root is the JSON object {"foo": "bar", "quux": true} */
const char *str;
int boolean;
json_unpack(root, "{s:s, s:b}", "foo", &str, "quux", &boolean);
assert(strcmp(str, "bar") == 0 && boolean == 1);
/* root is the JSON array [[1, 2], {"baz": null} */
json_error_t error;
json_unpack_ex(root, &error, JSON_VALIDATE_ONLY, "[[i,i], {s:n}]", "baz");
/* returns 0 for validation success, nothing is extracted */
/* root is the JSON array [1, 2, 3, 4, 5] */
int myint1, myint2;
json_unpack(root, "[ii!]", &myint1, &myint2);
/* returns -1 for failed validation */
/* root is an empty JSON object */
int myint = 0, myint2 = 0, myint3 = 0;
json_unpack(root, "{s?i, s?[ii]}",
"foo", &myint1,
"bar", &myint2, &myint3);
/* myint1, myint2 or myint3 is no touched as "foo" and "bar" don't exist */
Testing for equality of two JSON values cannot, in general, be achieved using the == operator. Equality in the terms of the == operator states that the two :type:`json_t` pointers point to exactly the same JSON value. However, two JSON values can be equal not only if they are exactly the same value, but also if they have equal “contents”:
Because of reference counting, passing JSON values around doesn’t require copying them. But sometimes a fresh copy of a JSON value is needed. For example, if you need to modify an array, but still want to use the original afterwards, you should take a copy of it first.
Jansson supports two kinds of copying: shallow and deep. There is a difference between these methods only for arrays and objects. Shallow copying only copies the first level value (array or object) and uses the same child values in the copied value. Deep copying makes a fresh copy of the child values, too. Moreover, all the child values are deep copied in a recursive fashion.
Copying objects preserves the insertion order of keys.
Returns a shallow copy of value, or NULL on error.
Returns a deep copy of value, or NULL on error.
By default, Jansson uses malloc() and free() for memory allocation. These functions can be overridden if custom behavior is needed.
Fetch the current malloc_fn and free_fn used. Either parameter may be NULL.
New in version 2.8.
Examples:
Circumvent problems with different CRT heaps on Windows by using application’s malloc() and free():
json_set_alloc_funcs(malloc, free);
Use the Boehm’s conservative garbage collector for memory operations:
json_set_alloc_funcs(GC_malloc, GC_free);
Allow storing sensitive data (e.g. passwords or encryption keys) in JSON structures by zeroing all memory when freed:
static void *secure_malloc(size_t size)
{
/* Store the memory area size in the beginning of the block */
void *ptr = malloc(size + 8);
*((size_t *)ptr) = size;
return ptr + 8;
}
static void secure_free(void *ptr)
{
size_t size;
ptr -= 8;
size = *((size_t *)ptr);
guaranteed_memset(ptr, 0, size + 8);
free(ptr);
}
int main()
{
json_set_alloc_funcs(secure_malloc, secure_free);
/* ... */
}
For more information about the issues of storing sensitive data in memory, see http://www.dwheeler.com/secure-programs/Secure-Programs-HOWTO/protect-secrets.html. The page also explains the guaranteed_memset() function used in the example and gives a sample implementation for it.