1. 23 Mar, 2017 1 commit
  2. 23 Feb, 2017 2 commits
  3. 04 Feb, 2017 1 commit
    • StilesCrisis's avatar
      Added unit test for pull parsing · 82a423db
      StilesCrisis authored
      New unit test which ensures that IterativeParseNext always generates
      exactly one element at a time, and that calling IterativeParseNext on a
      complete document is harmless and generates zero events.
      82a423db
  4. 24 Jan, 2017 1 commit
  5. 27 Jun, 2016 1 commit
  6. 23 Jun, 2016 1 commit
    • Philipp A. Hartmann's avatar
      Fix warnings on GCC 6 and later (closes #666) · f6a07692
      Philipp A. Hartmann authored
      * document.h
        * suppress -Wterminate on GCC 6.x and later
        * simplify warning handling
      * schema.h
        * drop RAPIDJSON_NOEXCEPT from GenericSchemaDocument constructor
          (calls RAPIDJSON_NEW anyway)
        * simplify warning handling
          (avoids RAPIDJSON_POP mismatch on Clang)
      * encodingtest.cpp, istreamwrappertest.cpp
        * work around -Wdangling-else
      * readertest.cpp
        * suppress -Wdangling-else
      f6a07692
  7. 20 May, 2016 1 commit
    • Michael Thon's avatar
      Allow options for writing and parsing NaN/Infinity · 135da7ab
      Michael Thon authored
      This adds kWriteNanAndInfFlag to Writer to allow writing of nan,
      inf and -inf doubles as "NaN", "Infinity" and "-Infinity",
      respectively, and kParseNanAndInfFlag to Reader to allow parsing
      of "NaN", "Inf", "Infinity", "-Inf" and "-Infinity". This is part
      of issue #36, adding optional support for relaxed JSON syntax.
      135da7ab
  8. 04 Apr, 2016 1 commit
  9. 29 Mar, 2016 1 commit
    • Jarred Nicholls's avatar
      Later clang compilers will warn on float -> double promotion because it can add… · 926d7ffc
      Jarred Nicholls authored
      Later clang compilers will warn on float -> double promotion because it can add precision. In the context of RapidJSON – especially with its float methods on GenericValue – I think this warning holds no water and should be ignored.
      
      Trim whitespace off the end of various lines.
      
      Added an additional NumberStream specialization that will always perform a TakePush() even when just Take() is called. This supports RawNumber parsing by pushing onto our StackStream particular parts of the number that currently aren't captured because of full precision double parsing, such as the negative sign, scientific number exponents, etc.
      
      RawNumber parsing fails with input streams that don't have copy optimization, such as the BasicIStreamWrapper stream. To work around this, instead do the Transcode copy operation by reading from a UTF8 StringStream instead of the original InputStream. Since the NumberStream downcasts all input Ch into chars, we know we're dealing with UTF8/ASCII compatible stack characters during the Transcoding.
      926d7ffc
  10. 20 Mar, 2016 3 commits
  11. 04 Mar, 2016 1 commit
  12. 02 Mar, 2016 2 commits
  13. 29 Feb, 2016 2 commits
  14. 13 Feb, 2016 1 commit
  15. 09 Feb, 2016 2 commits
  16. 03 Feb, 2016 1 commit
  17. 23 Jan, 2016 1 commit
  18. 22 Jan, 2016 2 commits
  19. 20 Jan, 2016 1 commit
  20. 18 Dec, 2015 5 commits
  21. 13 Oct, 2015 1 commit
    • Andrey's avatar
      Comments parsing fixes. · f7960ac0
      Andrey authored
      * Comments parsing function correctly handles EOF.
      * Since SkipWhitespaceAndComments can generate errors, its calls should be followed by RAPIDJSON_PARSE_ERROR_EARLY_RETURN macro.
      * Some tests to make the bug never appear again.
      f7960ac0
  22. 11 Oct, 2015 1 commit
  23. 14 May, 2015 1 commit
  24. 24 Apr, 2015 3 commits
  25. 18 Apr, 2015 1 commit
  26. 15 Apr, 2015 2 commits