Exit Zen
28
:103
English
When `allow_invalid_utf16` is enabled, the parser will not throw an error in the case of illegal leading, trailing, or half a surrogate. Instead, it will replace the invalid UTF-16 code point(s) with the Unicode replacement character.
89/2340 · 234
29
:113
English
When enabling comment support take extra care not to drop whitespace
22/680 · 68
30
:114
English
when reading the input. For example, `std::getline` removes the endline characters from the string it produces.
40/1110 · 111
31
:117
English
Full Precision Number Parsing
7/290 · 29
32
:118
English
The default algorithm that the library uses to parse numbers is fast, but may result in slight precision loss. This may not be suitable for some applications, so there is an option to enable an alternative algorithm that doesn't have that flaw, but is somewhat slower. To do this, you also need to use <<ref_parse_options>> structure.
130/3340 · 334
33
:129
English
Note that full precision number parsing requires the algorithm to see the full number. This means, that when used with <<ref_stream_parser>>, additional memory allocations may be necessary to store the number parts which were so far accepted by the parser. The library does try its best to avoid such allocations.
123/3130 · 313
34
:135
English
Parser
3/100 · 6
35
:136
English
Instances of <<ref_parser>> and <<ref_stream_parser>> offer functionality beyond what is available when using the <<ref_parse>> free functions:
142/1430 · 143
36
:139
English
More control over memory
9/240 · 24
37
:140
English
Streaming API, parse input JSON incrementally
20/450 · 45
38
:141
English
Improved performance when parsing multiple JSON texts
16/530 · 53
39
:142
English
Ignore non-JSON content after the end of a JSON text
20/520 · 52
40
:144
English
The parser implementation uses temporary storage space to accumulate values during parsing. When using the <<ref_parse>> free functions, this storage is allocated and freed in each call. However, by declaring an instance of <<ref_parser>> or <<ref_stream_parser>>, this temporary storage can be reused when parsing more than one JSON text, reducing the total number of dynamic memory allocations.
217/3960 · 396
41
:151
English
To use the <<ref_parser>>, declare an instance. Then call <<ref_parser_write>> once with the buffer containing representing the input JSON. Finally, call <<ref_parser_release>> to take ownership of the resulting <<ref_value>> upon success. This example persists the parser instance in a class member to reuse across calls:
250/3220 · 322
42
:162
English
Sometimes a protocol may have a JSON text followed by data that is in a different format or specification. The JSON portion can still be parsed by using the function <<ref_parser_write_some>>. Upon success, the return value will indicate the number of characters consumed from the input, which will exclude the non-JSON characters:
151/3310 · 331
43
:173
English
The parser instance may be constructed with parse options which allow some non-standard JSON extensions to be recognized:
36/1210 · 121
44
:181
English
Streaming Parser
5/160 · 16
45
:182
English
The <<ref_stream_parser>> implements a https://en.wikipedia.org/wiki/Online_algorithm[__streaming algorithm__]; it allows incremental processing of large JSON inputs using one or more contiguous character buffers. The entire input JSON does not need to be loaded into memory at once. A network server can use the streaming interface to process incoming JSON in fixed-size amounts, providing these benefits:
198/4060 · 406
46
:189
English
CPU consumption per I/O cycle is bounded
22/400 · 40
47
:190
English
Memory consumption per I/O cycle is bounded
19/430 · 43