amorfo77/json
1
0
Fork 0
mirror of https://github.com/nlohmann/json.git synced 2026-08-21 00:23:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: b5378e8deb

Browse Source
This commit is contained in:
nlohmann
2026-08-19 18:20:55 +00:00
parent b4e4dbe346
commit e5ef5a4cd3
261 changed files with 4526 additions and 4483 deletions
Download Patch File Download Diff File Expand all files Collapse all files
features/binary_formats/cbor/index.html
+7 -7
View File
File diff suppressed because one or more lines are too long
features/binary_formats/cbor/index.md
+3 -6
View File
@@ -174,14 +174,11 @@ Incomplete mapping
The mapping is **incomplete** in the sense that not all CBOR types can be converted to a JSON value. The following CBOR types are not supported and will yield parse errors:
- date/time (0xC0..0xC1)
- bignum (0xC2..0xC3)
- decimal fraction (0xC4)
- bigfloat (0xC5)
- expected conversions (0xD5..0xD7)
- simple values (0xE0..0xF3, 0xF8)
- undefined (0xF7)
Tagged items (0xC0..0xDB) are not interpreted either; see the note on tagged items below.
Negative integer overflow
CBOR negative integers (major type 1) are decoded as `-1 - n`. If the encoded magnitude `n` is too large for the result to fit into `number_integer_t` (`std::int64_t` by default), parsing fails with a [`parse_error.112`](https://json.nlohmann.me/home/exceptions/#jsonexceptionparse_error112) exception rather than overflowing silently.
@@ -192,7 +189,7 @@ CBOR allows map keys of any type, whereas JSON only allows strings as keys in ob
Tagged items
Tagged items will throw a parse error by default. They can be ignored by passing `cbor_tag_handler_t::ignore` to function `from_cbor`. They can be stored by passing `cbor_tag_handler_t::store` to function `from_cbor`.
Tagged items (0xC0..0xDB) will throw a parse error by default. They can be ignored by passing `cbor_tag_handler_t::ignore` to function `from_cbor`, in which case the tag is skipped and the enclosed data item is parsed on its own. They can be stored by passing `cbor_tag_handler_t::store` to function `from_cbor`. Note that no tag is ever interpreted: for instance, a text string tagged with tag 0 (date/time) stays a string.
Example