2. Boost Json Translation (zh_Hans)
3. English
4. Zen

51 :157
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To use the resource, construct it with a local buffer: 54/10000 · 54
51 :200
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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: 198/10000 · 198
52 :115
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Embedded 8/10000 · 8
52 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — mesh.json with whitespace added. 32/10000 · 32
52 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_emplace_uint64>> 28/10000 · 28
52 :116
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `std::filesystem::path` and similar types, e.g. `boost::filesystem::path`. 74/10000 · 74
52 :164
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Null Resource 13/10000 · 13
52 :204
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This example will break, if comments are enabled, because of 60/10000 · 60
53 :117
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Boost.JSON works great on embedded devices. The library uses local stack buffers to increase the performance of some operations. On Intel platforms these buffers are large (4KB), while on non-Intel platforms they are small (256 bytes). To adjust the size of the stack buffers for embedded applications define this macro when building the library or including the function definitions: 384/10000 · 384
53 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<parse_numbers_json,*numbers.json*>> 37/10000 · 37
53 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_is_uint64>> 23/10000 · 23
53 :116
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The result is equal to the result of `path::generic_string`. 60/10000 · 60
53 :165
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The function <<ref_get_null_resource>> returns a global instance of the null resource. This resource offers a simple invariant: all calls to allocate will throw the exception `std::bad_alloc`. An instance of the null resource can be used to make parsing guarantee that allocations from the heap are never made. This is explored in more detail in a later section. 362/10000 · 362
53 :205
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `std::getline` use (see the warning in <<non_standard_json>> section). 70/10000 · 70
54 :129
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Supported Compilers 19/10000 · 19
54 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 147KB 5/10000 · 5
54 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_if_uint64>> 23/10000 · 23
54 :116
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The result is constructed from two pointers to `const char`. 60/10000 · 60
54 :171
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Allocator Propagation 21/10000 · 21
54 :212
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — We can complicate the example further by extracting _several_ JSON values from the sequence of lines. 101/10000 · 101