json-c

Commit Graph

Author	SHA1	Message	Date
Eric Hawicz	565f181f65	Fix issue #875 : cast to unsigned char so bytes above 0x7f aren't interpreted as negative, which was causing the strict-mode control characters check to incorrectly trigger.	10 months ago
Eric Hawicz	87900c0a2e	Fix the expected output for test_parse	1 year ago
Eric Haszlakiewicz	bc35549f90	Update expected output for test_parse, missed in the previous commit.	2 years ago
Eric Haszlakiewicz	f23486a321	In the json_tokener_state_number case, explicitly adjust what "number" characters are allowed based on the exact micro-state that we're in, and check for invalid following characters in a different way, to allow a valid json_type_number object to be returned at the top level. This causes previously failing strings like "123-456" to return a valid json_object with the appropriate value. If you care about the trailing content, call json_tokener_parse_ex() and check the parse end point with json_tokener_get_parse_end().	5 years ago
Eric Haszlakiewicz	6eac6986c9	Fix incremental parsing of invalid numbers with exponents, such as "0e+-" and "12.3E12E12", while still allowing "0e+" in non-strict mode. Deprecate the json_parse_double() function from json_util.h	5 years ago
Eric Haszlakiewicz	a68566bf6a	Issue #616 : Change the parsing of surrogate pairs in unicode escapes so it uses a couple of additional states instead of assuming the low surrogate is already present, to ensure that we correctly handle various cases of incremental parsing.	5 years ago
Eric Haszlakiewicz	197e372464	In test_parse, fix lengths passed during a couple of incremental tests. Add an optional way to use an incremental chunk size ($TEST_PARSE_CHUNKSIZE) for all of the single_basic_parse tests, in additional to the regular way.	5 years ago
dota17	c1b872d817	fix issue 616: support the surrogate pair in split file.	5 years ago
Eric Haszlakiewicz	f6f76f9430	Add a JSON_TOKENER_ALLOW_TRAILING_CHARS flag for json_tokener_set_flags() to allow multiple objects to be parsed from input even when JSON_TOKENER_STRICT is set.	5 years ago
dota17	3c3b5920f7	add uint64 data to json-c	5 years ago
dota17	787a8b3f1c	update code	5 years ago
dota17	eca74dcccf	test utf8	5 years ago
dota17	5fe4448541	update tsetcase for tokener_c	5 years ago
chenguoping	1446572997	add testcases of object and token	5 years ago
Eric Haszlakiewicz	da4b34355d	Add an parse test for content starting with a UTF8 BOM, which is _not_ a valid start to a JSON message.	7 years ago
Eric Haszlakiewicz	9c9529f798	Update test_parse.expected to match the code.	7 years ago
Eric Haszlakiewicz	ba11d334db	Save proper expected output for test_parse from the previous commit.	7 years ago
Eric Haszlakiewicz	4d1e0b4409	Issue #371 : fix parsing of "-Infinity" (although in a somewhat different location than PR#372 used), and add a case to test_parse to check for this.	7 years ago
Eric Haszlakiewicz	2a22858fe7	Add a few extra cases to test_parse to show how trailing bytes are handled, especially for parsing "Infinity".	7 years ago
Eric Haszlakiewicz	b8738dd623	Rewrite test_basic_parse() to factor out a single_basic_parse() to avoid lots of duplicate boiler plate code. Also, emit the input string in the output so it's easier to see what's going on.	7 years ago
Eric Haszlakiewicz	8c86207258	Add a few more cases to test_parse to provide some examples of how parsing works; should help address the questions raised in Issue #302 .	8 years ago
Jan Gerhards	ca7a1973e2	bugfix: floating point representaion without fractional part closes https://github.com/json-c/json-c/issues/278	8 years ago
Eric Haszlakiewicz	33339ae595	Use json_visit() to clear the serializer data set when parsing so the output from test_parse reflects the actual values parsed.	9 years ago
Eric Haszlakiewicz	36a28fcb0c	Issue #275 : fix out of bounds read when handling unicode surrogate pairs.	9 years ago
Eric Haszlakiewicz	316da85818	Fix issue #201 : add a JSON_C_TO_STRING_NOSLASHESCAPE flag to turn off escaping of forward slashes.	9 years ago
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

33 Commits (51bcdd0000263d6e768911d1ac5f5733dbc344d9)