Exit Zen
20
:44
English
parsers use this internally, and users may use it to adapt foreign parsers to produce this library's containers. |===
39/1170 · 117
21
:48
English
The <<ref_parse>> function offers a simple interface for converting a serialized JSON text to a <<ref_value>> in a single function call. This overload uses exceptions to indicate errors:
113/1860 · 186
22
:57
English
Alternatively, an {ref_error_code} can be used:
24/470 · 47
23
:64
English
Even when using error codes, exceptions thrown from the underlying {ref_memory_resource} are still possible:
41/1080 · 108
24
:72
English
The <<ref_value>> returned in the preceding examples use the <<default_memory_resource,default memory resource>>. The following code uses a <<ref_monotonic_resource>>, which results in faster parsing. `jv` is marked `const` to prevent subsequent modification, because containers using a monotonic resource waste memory when mutated.
277/3320 · 332
25
:83
English
Non-Standard JSON
7/170 · 17
26
:84
English
Unless otherwise specified, the parser in this library is strict. It recognizes only valid, standard JSON. The parser can be configured to allow certain non-standard extensions by filling in a <<ref_parse_options>> structure and passing it by value. By default all extensions are disabled:
131/2890 · 289
27
:94
English
When building with {cpp}20 or later, the use of https://en.cppreference.com/w/cpp/language/aggregate_initialization#Designated_initializers[designated initializers] with <<ref_parse_options>> is possible:
176/2040 · 204
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