This also requires turning off the c++98 compatibility checks when building
with clang.

Refactor regex

Remove mutable which causes reentrant issue

Add preconditions in writer and string functions

Fix typo in doc

fix wrong length in remote schema

Change-Id: Ia96ddf5746f1c18968e9e086f17fe4a24b8480d7

Remove non-compiling assignment operator

Version 1.1.0

Change version numbers
Fixed some document linkage
Fix #648

Fix builds on x32 platform.

From the Debian wiki: https://wiki.debian.org/X32Port

X32 is an ABI for amd64/x86_64 CPUs using 32-bit integers, longs
and pointers. The idea is to combine the smaller memory and cache
footprint from 32-bit data types with the larger register set of
x86_64. The 64-bit registers can make computation more efficient,
and with 8 additional registers available, there is less pressure
compared to i386/i686.

rapidjson makes an incorrect assumption in a check for 64 bit
platforms, and uses __LP64__ exclusively. This fix adds an
additional check for __x86_64__ && __ILP32__ defines, as a very
conservative fix. However, the usage of __LP64__ would be a problem
for other "mixed" applications like ARM ILP32, so a better detection
scheme might be needed in the future.

Add std::string overload to PrettyWriter::Key() when RAPIDJSON_HAS_STDSTRING is #defined

Only String() has the std::string overload currently.

Handle malloc() fail in PoolAllocator

Fix #682

optimize FindMember  when use std::string

Add Flush() for all value types

Fixes #684

also use internal::StrLen to get the string lengtht,
when it call FindMember(StringRef(name)).
Now use GenericValue construct it, then can use the std::string.size.
now it will be faster.

fix rapidjson::value::Get<std::string>() may returns wrong data

Change-Id: Ia7325edb437e3039e29223d0ecc4d9c83d824bc0

Make GenericSchemaDocument constructor explicit

Prior to this change, a user could incorrectly pass a Document object to
SchemaValidator. This would implicitly construct a SchemaDocument, which
would then be destructed before the validator was used. This caused
unpredictable results including memory corruption and program crashes.

Fix buffer overrun using PutN (closes #672)

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.

readertest: Suppress "dangling-else" warning on GCC 7 and later

GCC 6.x doesn't yet support this warning flag, as reported by
@ragnar-ouchterlony.

Fix warnings on GCC 6 and later (closes #666)

document typo fix and .gitignore update