amorfo77/json
1
0
Fork 0
mirror of https://github.com/nlohmann/json.git synced 2026-10-05 14:10:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: 6b4b825af2

Browse Source
This commit is contained in:
nlohmann
2026-10-05 05:14:25 +00:00
parent c51ca275d0
commit f99a460b9b
18 changed files with 317 additions and 307 deletions
Download Patch File Download Diff File Expand all files Collapse all files
features/binary_formats/cbor/index.html
+2 -2
View File
File diff suppressed because one or more lines are too long
features/binary_formats/cbor/index.md
+1 -1
View File
@@ -181,7 +181,7 @@ Tagged items (0xC0..0xDB) are not interpreted either; see the note on tagged ite
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.
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), the result is stored as `number_float_t`, like a too small integer in JSON text. For example, `-18446744073709551616` (`0x3B` followed by eight `0xFF` bytes) is stored as `-1.8446744073709552e+19`.
Object keys