Exit Zen
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
48
:191
English
Jitter, unfairness, and latency is reduced
12/420 · 42
49
:192
English
Less total memory is required to process the full input
14/550 · 55
50
:194
English
To use the <<ref_stream_parser>>, declare an instance. Then call <<ref_stream_parser_write>> zero or more times with successive buffers representing the input JSON. When there are no more buffers, call <<ref_stream_parser_finish>>. The function <<ref_stream_parser_done>> returns `true` after a successful call to `write` or `finish` if parsing is complete.
324/3570 · 357
51
:200
English
In the following example a JSON text is parsed from standard input a line at a time. Error codes are used instead. The function <<ref_stream_parser_finish>> is used to indicate the end of the input:
107/1980 · 198
52
:204
English
This example will break, if comments are enabled, because of
17/600 · 60