@@ -97,6 +97,7 @@ json.exception.parse_error.110 | parse error at 1: cannot read 2 bytes from vect
json.exception.parse_error.112 | parse error at 1: error reading CBOR; last byte: 0xF8 | Not all types of CBOR or MessagePack are supported. This exception occurs if an unsupported byte was read.
json.exception.parse_error.113 | parse error at 2: expected a CBOR string; last byte: 0x98 | While parsing a map key, a value that is not a string has been read.
json.exception.parse_error.114 | parse error: Unsupported BSON record type 0x0F | The parsing of the corresponding BSON record type is not implemented (yet).
json.exception.parse_error.115 | parse error at byte 5: syntax error while parsing UBJSON high-precision number: invalid number text: 1A | A UBJSON high-precision number could not be parsed.
@note For an input with n bytes, 1 is the index of the first character and n+1
is the index of the terminating null byte or the end of file. This also
returnsax->parse_error(chars_read,s,parse_error::create(115,chars_read,exception_message(input_format_t::ubjson,"invalid number text: "+s,"high-precision number")));
returnsax->parse_error(chars_read,s,parse_error::create(115,chars_read,exception_message(input_format_t::ubjson,"invalid number text: "+s,"high-precision number")));
@@ -2280,6 +2280,7 @@ json.exception.parse_error.110 | parse error at 1: cannot read 2 bytes from vect
json.exception.parse_error.112 | parse error at 1: error reading CBOR; last byte: 0xF8 | Not all types of CBOR or MessagePack are supported. This exception occurs if an unsupported byte was read.
json.exception.parse_error.113 | parse error at 2: expected a CBOR string; last byte: 0x98 | While parsing a map key, a value that is not a string has been read.
json.exception.parse_error.114 | parse error: Unsupported BSON record type 0x0F | The parsing of the corresponding BSON record type is not implemented (yet).
json.exception.parse_error.115 | parse error at byte 5: syntax error while parsing UBJSON high-precision number: invalid number text: 1A | A UBJSON high-precision number could not be parsed.
@note For an input with n bytes, 1 is the index of the first character and n+1
is the index of the terminating null byte or the end of file. This also
returnsax->parse_error(chars_read,s,parse_error::create(115,chars_read,exception_message(input_format_t::ubjson,"invalid number text: "+s,"high-precision number")));
returnsax->parse_error(chars_read,s,parse_error::create(115,chars_read,exception_message(input_format_t::ubjson,"invalid number text: "+s,"high-precision number")));
}
}
...
...
@@ -23881,6 +23897,7 @@ class basic_json
int16 | number_integer | `I`
int32 | number_integer | `l`
int64 | number_integer | `L`
high-precision number | number_integer, number_unsigned, or number_float - depends on number string | 'H'
string | string | `S`
char | string | `C`
array | array (optimized values are supported) | `[`
CHECK_THROWS_WITH_AS(json::from_ubjson(vec1),"[json.exception.parse_error.115] parse error at byte 5: syntax error while parsing UBJSON high-precision number: invalid number text: 1A",json::parse_error);
std::vector<uint8_t>vec2={'H','i',2,'1','.'};
CHECK_THROWS_WITH_AS(json::from_ubjson(vec2),"[json.exception.parse_error.115] parse error at byte 5: syntax error while parsing UBJSON high-precision number: invalid number text: 1.",json::parse_error);
std::vector<uint8_t>vec3={'H',2,'1','0'};
CHECK_THROWS_WITH_AS(json::from_ubjson(vec3),"[json.exception.parse_error.113] parse error at byte 2: syntax error while parsing UBJSON size: expected length type specification (U, i, I, l, L) after '#'; last byte: 0x02",json::parse_error);