json-c

4.5 MB

Tree: 99d8fc975e

Author	SHA1	Message	Date
chl	99d8fc975e	Tightening the number parsing algorithm Some badly formated "numbers" could get partly parsed, resulting in truncated results instead of raising an error. Examples : '1.2.3' -> (double)1.2 '2015-01-15' -> (int)2015 This patch is not perfect (ex: input can still end with a 'E', which is forbidden by json.org doc) but should avoid non-sensically formated input. Tests added.	10 years ago
Eric Haszlakiewicz	05da316b9c	Issue #103 : allow Infinity and -Infinity to be parsed.	11 years ago
Eric Haszlakiewicz	0eedf3802f	Issue#102 - add support for parsing "NaN".	11 years ago
Eric Haszlakiewicz	51993c28c2	Added a json_object_new_double_s() convenience function to allow an exact string representation of a double to be specified when creating the object and use it in json_tokener_parse_ex() so a re-serialized object more exactly matches the input. Add json_object_free_userdata() and json_object_userdata_to_json_string() too.	12 years ago
Eric Haszlakiewicz	e8161a11bb	Issue #15 : add a way to set a JSON_TOKENER_STRICT flag to forbid commas at the end of arrays and objects.	12 years ago
Iskren Chernev	78b089bc1e	Fixed test_parse for \f	12 years ago
Eric Haszlakiewicz	92f31bd99a	Handle the \f escape sequence (the two characters: backslash followed by an f, not a literal formfeed) and extend the test_parse test to check all valid escape sequences.	13 years ago
Eric Haszlakiewicz	c1b8891a13	Move the rest of the tests into the tests subdirectory.	13 years ago