conformance.rst (jansson-2.13.1.tar.bz2) | : | conformance.rst (jansson-2.14.tar.bz2) | ||
---|---|---|---|---|
skipping to change at line 25 | skipping to change at line 25 | |||
UTF-16LE, UTF-16BE, UTF-32LE or UTF-32BE. Pure ASCII is supported, as | UTF-16LE, UTF-16BE, UTF-32LE or UTF-32BE. Pure ASCII is supported, as | |||
it's a subset of UTF-8. | it's a subset of UTF-8. | |||
Strings | Strings | |||
======= | ======= | |||
JSON strings are mapped to C-style null-terminated character arrays, | JSON strings are mapped to C-style null-terminated character arrays, | |||
and UTF-8 encoding is used internally. | and UTF-8 encoding is used internally. | |||
All Unicode codepoints U+0000 through U+10FFFF are allowed in string | All Unicode codepoints U+0000 through U+10FFFF are allowed in string | |||
values. However, U+0000 is not allowed in object keys because of API | values. However, U+0000 is allowed in object keys only for length-aware function | |||
restrictions. | s. | |||
Unicode normalization or any other transformation is never performed | Unicode normalization or any other transformation is never performed | |||
on any strings (string values or object keys). When checking for | on any strings (string values or object keys). When checking for | |||
equivalence of strings or object keys, the comparison is performed | equivalence of strings or object keys, the comparison is performed | |||
byte by byte between the original UTF-8 representations of the | byte by byte between the original UTF-8 representations of the | |||
strings. | strings. | |||
Numbers | Numbers | |||
======= | ======= | |||
skipping to change at line 113 | skipping to change at line 112 | |||
No support is provided in Jansson for any C numeric types other than | No support is provided in Jansson for any C numeric types other than | |||
``json_int_t`` and ``double``. This excludes things such as unsigned | ``json_int_t`` and ``double``. This excludes things such as unsigned | |||
types, ``long double``, etc. Obviously, shorter types like ``short``, | types, ``long double``, etc. Obviously, shorter types like ``short``, | |||
``int``, ``long`` (if ``json_int_t`` is ``long long``) and ``float`` | ``int``, ``long`` (if ``json_int_t`` is ``long long``) and ``float`` | |||
are implicitly handled via the ordinary C type coercion rules (subject | are implicitly handled via the ordinary C type coercion rules (subject | |||
to overflow semantics). Also, no support or hooks are provided for any | to overflow semantics). Also, no support or hooks are provided for any | |||
supplemental "bignum" type add-on packages. | supplemental "bignum" type add-on packages. | |||
Depth of nested values | Depth of nested values | |||
====================== | ||||
To avoid stack exhaustion, Jansson currently limits the nesting depth | To avoid stack exhaustion, Jansson currently limits the nesting depth | |||
for arrays and objects to a certain value (default: 2048), defined as | for arrays and objects to a certain value (default: 2048), defined as | |||
a macro ``JSON_PARSER_MAX_DEPTH`` within ``jansson_config.h``. | a macro ``JSON_PARSER_MAX_DEPTH`` within ``jansson_config.h``. | |||
The limit is allowed to be set by the RFC; there is no recommended value | The limit is allowed to be set by the RFC; there is no recommended value | |||
or required minimum depth to be supported. | or required minimum depth to be supported. | |||
End of changes. 2 change blocks. | ||||
2 lines changed or deleted | 3 lines changed or added |