Exit Zen
1
:11
English
= Frequently Asked Questions
6/280 · 28
1
:12
English
= Examples
4/100 · 10
1
:11
English
= Boost.JSON (C) 2019--2020 Vinnie Falco; (C) 2020 Krystian Stasiowski; (C) 2022 Dmitry Arkhipov :idprefix: :sectanchors: :toclevels: 2 :toc: left :pagelevels: 2 :source-highlighter: rouge :source-language: c++
210/2100 · 210
1
:11
English
= Background The first version of allocators in C++ defined the named requirement {req_Allocator}, and made each standard container a class template parameterized on the allocator type. For example, here is the declaration for {std_vector}:
93/2400 · 240
1
:12
English
= Allocators
5/120 · 12
1
:11
English
= Reference
4/110 · 11
1
:12
English
= Uses-allocator Construction To support code bases which are already using polymorphic allocators, the containers in this library support {std_uses_allocator} construction. For <<ref_array>>, <<ref_object>>, <<ref_string>>, and <<ref_value>>:
198/2430 · 243
1
:12
English
= Parsing Parsing is the process where a serialized JSON text is validated and decomposed into elements. The library provides these functions and types to assist with parsing:
48/1750 · 175
1
:12
English
= Quick Look Here we highlight important features through example code to help convey the style of the interface. We begin by including the library header file which brings all the symbols into scope. Alternatively, individual headers may be included to obtain the declarations for specific types:
84/2970 · 297
1
:12
English
= Benchmarks This section compares the performance of Boost.JSON with two widely used libraries with similar functionality: RapidJSON which is known for its performance, and JSON for Modern C++ which is known for feature-richness. The bench program measures the throughput of parsing and serialization for the a set of JSON representing typical workloads. These implementations are evaluated:
155/3920 · 392
1
:12
English
= Comparison to Other Libraries
9/310 · 31
1
:11
English
= Serializing
5/130 · 13
1
:12
English
= Input/Output The library provides parsing and serialization algorithms to transform JSON to and from the <<ref_value>> container as needed. This is accomplished through free functions and classes, described as follows.
97/2200 · 220
1
:10
English
:ref_memory_resource: pass:q[https://boost.org/doc/libs/latest/doc/html/doxygen/boost_container_header_reference/classboost_1_1container_1_1pmr_1_1memory__resource.html[`memory_resource`]] :ref_polymorphic_allocator: pass:q[https://boost.org/doc/libs/latest/doc/html/doxygen/boost_container_header_reference/classboost_1_1container_1_1pmr_1_1polymorphic__allocator.html[`polymorphic_allocator`]] :ref_error_category: pass:q[https://boost.org/doc/libs/latest/libs/system/doc/html/system.html#ref_error_category[`error_category`]] :ref_error_code: pass:q[https://boost.org/doc/libs/latest/libs/system/doc/html/system.html#ref_error_code[`error_code`]] :ref_error_condition: pass:q[https://boost.org/doc/libs/latest/libs/system/doc/html/system.html#ref_error_condition[`error_condition`]] :ref_result: pass:q[https://boost.org/doc/libs/latest/libs/system/doc/html/system.html#ref_resultt_e[`result`]] :ref_system_error: pass:q[https://boost.org/doc/libs/latest/libs/system/doc/html/system.html#ref_system_error[`system_error`]]
1078/10780 · 1078
1
:11
English
= Initializer Lists Initializer lists can be used to construct or assign a <<ref_value>>:
55/890 · 89
1
:13
English
= Value Conversion While the <<ref_value>> container makes it easy to create ad-hoc structures, often it is necessary to convert between JSON and user-defined types or types from the standard library.
85/2000 · 200
2
:4
English
Branch
2/100 · 6
2
:21
English
This is particularly useful when throwing exceptions is undesirable. For example, compare
30/890 · 89
2
:18
English
Type
53/100 · 4
2
:15
English
Modifiable sequences of characters are represented using objects of type <<ref_string>>.
53/880 · 88