Exit Zen
:95
:95
English
<<ref_kind,`kind::double_`>>
61/280 · 28
58
:185
English
It is important to note that <<ref_storage_ptr>> supports both shared-ownership and reference lifetime models. Construction from a memory resource pointer does not transfer ownership:
88/1830 · 183
58
:248
English
Avoiding Dynamic Allocations
6/280 · 28
58
:90
English
A JSON with lots of Cyrillic characters.
30/400 · 40
58
:139
English
include::custom.adoc[] include::nothrow.adoc[] include::alloc.adoc[] include::context.adoc[] include::forward.adoc[] include::direct.adoc[] include::guidelines.adoc[]
166/1660 · 166
59
:137
English
Supported JSON Text
11/190 · 19
59
:95
English
https://en.cppreference.com/w/cpp/language/types[`double`]
58/580 · 58
59
:194
English
When using a memory resource in this fashion, including the case where a storage pointer or container is constructed from a {ref_polymorphic_allocator}, the caller must ensure that the lifetime of the resource is extended until it is no longer referenced by any variables; otherwise, undefined behavior is possible.
102/3150 · 315
59
:249
English
Through careful specification of buffers and memory resources, it is possible to eliminate all dynamic allocation completely when parsing JSON, for the case where the entire JSON text is available in a single character buffer, as shown here:
68/2410 · 241
59
:90
English
<<parse_twitter_json,*twitter.json*>>
79/370 · 37
59
:147
English
:leveloffset: -1
16/160 · 16
60
:139
English
The library expects input text to be encoded using UTF-8, which is a requirement put on all JSON exchanged between systems by the https://datatracker.ietf.org/doc/html/rfc8259#section-8.1[RFC]. Similarly, the text generated by the library is valid UTF-8.
134/2540 · 254
60
:95
English
<<ref_value_emplace_double>>
61/280 · 28
60
:200
English
Shared ownership is achieved using the function <<ref_make_shared_resource>>, which creates a new, reference-counted memory resource using a dynamic memory allocation and returns it as a <<ref_storage_ptr>>:
160/2070 · 207
60
:259
English
Custom Parsers
6/140 · 14
60
:90
English
617KB
5/100 · 5
61
:144
English
The RFC does not allow byte order marks (BOM) to appear in JSON text, so the library considers BOM syntax errors.
48/1130 · 113
61
:95
English
<<ref_value_is_double>>
51/230 · 23
61
:209
English
When a storage pointer is constructed this way, the lifetime of the referenced memory resource is extended until all variables which reference it are destroyed.
49/1600 · 160
61
:260
English
Users who wish to implement custom parsing strategies may create their own handler to use with an instance of <<ref_basic_parser>>. The handler implements the function signatures required by SAX event interface. In <<examples_validate>> example we define the "null" parser, which throws out the parsed results, to use in the implementation of a function that determines if a JSON text is valid.
231/3940 · 394