13 Commits (ba8625a7016ba9bdbb4de1f7c461f67bccd1e9e2)

Author SHA1 Message Date
  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 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 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. 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