Issue 889

It did not support char arrays.

Lookahead Parser

Fix -Werror=effc++ errors with GNU 6.3.1

Fix "'MyHandler::type’ should be initialized in the member
initialization list [-Werror=effc++]" errors.

https://github.com/miloyip/rapidjson/issues/874

Fix "'MyHandler::type’ should be initialized in the member
initialization list [-Werror=effc++]" errors.

https://github.com/miloyip/rapidjson/issues/874

Use native strlen

Disambiguate by putting the ENABLEIF on the return value instead of in
the argument list.

Assert in case users attempt to pass a char array to String() or Key()
that is not null terminated; that is not the intended use of the API.
Null terminate your string buffers.

Same fix as previous commit, to prettywriter

No strlen call needs to be made when templates can auto-deduce the
string length. No strlen = faster!

Unfortunately this needs a touch of  SFINAE to allow multiple overrides
to coexist cleanly.

Remove executable bit

Remove the executable bit for various .json files

No-op blank line

Token-by-token parser documentation

Compilers generally provide a much smarter strlen than ours.

Make example code var names match API above for consistency

Writer EndObject missing-value fix

Null handler fix

We should not malloc the null-handler object and cast to OutputHandler;
we need to actually invoke the constructor via placement new.

Add unit test for Issue 848 (segfault in ~Document)

PrettyWriter EndObject will now also assert if called when a key is
missing its matching value.

Documented existing assertions in EndObject
Added new assertion in EndObject to catch error condition where objects
are ended with a key but no matching value.