- 15 Jun, 2017 1 commit
-
-
kyb authored
Fixed #985 : Unittest failed with MinGWx64. And few small improvement were done while looking for mistakes. Problem was because of Windows uses backslashes '\', not Unix '/'
-
- 09 Jun, 2017 1 commit
-
-
Milo Yip authored
Fix #825
-
- 12 May, 2017 1 commit
-
-
Milo Yip authored
-
- 21 Apr, 2017 1 commit
-
-
Alejandro Martinez authored
Change-Id: Iaf210d029758723a7eeb7f28fc10cab7467889a9 Signed-off-by:
Jun He <jun.he@arm.com>
-
- 27 Mar, 2017 1 commit
-
-
Milo Yip authored
-
- 24 Mar, 2017 1 commit
-
-
Alejandro Martinez authored
-
- 23 Mar, 2017 1 commit
-
-
Alejandro Martinez authored
-
- 15 Mar, 2017 1 commit
-
-
John Stiles authored
Missed PrettyWriter in the initial fix for Issue #889
-
- 13 Mar, 2017 1 commit
-
-
John Stiles authored
-
- 03 Mar, 2017 3 commits
-
-
John Stiles authored
-
John Stiles authored
-
John Stiles authored
-
- 01 Mar, 2017 2 commits
-
-
John Stiles authored
No-op blank line
-
John Stiles authored
-
- 28 Feb, 2017 3 commits
-
-
StilesCrisis authored
Add unit test for Issue 848 (segfault in ~Document)
-
StilesCrisis authored
PrettyWriter EndObject will now also assert if called when a key is missing its matching value.
-
StilesCrisis authored
Add unit tests expecting an assertion when writing an object with a key but no value.
-
- 23 Feb, 2017 2 commits
-
-
StilesCrisis authored
A failed half-consume of “NaN” now returns “value invalid” instead of attempting to consume an “Inf”.
-
StilesCrisis authored
Noticed that the reader could over-consume “NaN” if token terminated in the middle.
-
- 07 Feb, 2017 1 commit
-
-
John Stiles authored
Add more tests! Good for coverage.
-
- 04 Feb, 2017 1 commit
-
-
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.
-
- 03 Feb, 2017 1 commit
-
-
StilesCrisis authored
Add “filename” to the error message when JsonChecker reports an error.
-
- 24 Jan, 2017 1 commit
-
-
Milo Yip authored
Fix #824
-
- 19 Jan, 2017 1 commit
-
-
Zhihao Yuan authored
-
- 21 Dec, 2016 2 commits
-
-
Andrey Glebov authored
-
Andrey Glebov authored
-
- 17 Oct, 2016 1 commit
-
-
Milo Yip authored
-
- 05 Oct, 2016 1 commit
-
-
Milo Yip authored
Fixes #762
-
- 22 Sep, 2016 1 commit
-
-
Milo Yip authored
Fix #744
-
- 21 Sep, 2016 1 commit
-
-
Milo Yip authored
-
- 19 Sep, 2016 1 commit
-
-
Tallódi Mihály authored
-
- 16 Sep, 2016 1 commit
-
-
Milo Yip authored
Remove mutable which causes reentrant issue
-
- 31 Aug, 2016 1 commit
-
-
niukuo authored
Change-Id: Ia96ddf5746f1c18968e9e086f17fe4a24b8480d7
-
- 30 Jun, 2016 1 commit
-
-
Jason Smith authored
Fix inconsistent calling of template functions in PutN in stream.h. When used with a GenericStringBuffer<<UTF8>, MemoryPoolAllocator>, PutN would call PutReserve from stream.h, and PutUnsafe from stringbuffer.h. This resulted in bytes being added to the buffer without allocating space. This was not an issue when used with the default memory allocator, because in this case the specialized PutN is used from stringbuffer.h.
-
- 27 Jun, 2016 1 commit
-
-
Philipp A. Hartmann authored
GCC 6.x doesn't yet support this warning flag, as reported by @ragnar-ouchterlony.
-
- 23 Jun, 2016 1 commit
-
-
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
-
- 14 Jun, 2016 4 commits
-
-
Eli Fidler authored
-
Eli Fidler authored
note that std::numeric_limits<uint64_t>::max() and std::numeric_limits<int64_t>::max() aren't exactly representable in a double, so we need to be strictly less to be definitely lossless UBSAN gave during Value.IsLosslessDouble test: include/rapidjson/document.h:955:42: runtime error: value 1.84467e+19 is outside the range of representable values of type 'unsigned long'
-
Eli Fidler authored
UBSAN gave: runtime error: division by zero
-
Eli Fidler authored
maybe these tests should just be deleted? UBSAN gave: runtime error: signed integer overflow: -9223372036854775808 - 1 cannot be represented in type 'long' runtime error: signed integer overflow: -9223372036854775808 - 2 cannot be represented in type 'long'
-