This is a bit awkward since preserving correct indentation structure requires
a bit of extra work, and the closing tag has to be written by _start function
to correctly process the rest of the tree.

When this flag is true, PCDATA value is saved to the parent element instead of
allocating a new node.

This prevents some documents from round-tripping since it loses information,
but can provide a significant memory reduction and parsing speedup for some
documents.

Also refactor to use the same case and run after common options.

scripts: Allow linking static CRT libraries on Windows

Use the solution from CMake FAQ to specify correct command-line arguments.

(!"string") triggers the warning however (false && "string") does not.

Fixes #75.

Apparently some MinGW distributions have a compiler that's recent enough to
support C++11 but limits.h header that incorrectly omits LLONG limits in
strict ANSI mode, since it guards the definitions with:

	#if !defined(__STRICT_ANSI__) && defined(__GNUC__)

We can just define these symbols ourselves in this specific case.

Fixes #66.

The tests now compile fine but crash on the first floating-point exception
despite our attempts to disable them in main()...

It does not have stdint.h and has some C++ parsing issues.

Fixes #61.

For some reason reference to a fixed-size array works in two other places
but not in this one...

These show up when building with Wcast-align for ARM.

Travis CI strikes once more.

It now also moves parse result.

Only happens on GCC 3.4 for some reason.

Fix "this decimal constant is unsigned only in ISO C90".

name_sentry dtor results in multiple symbol definition errors in MSVC6.

Since they don't contribute to the resulting value just skip them before
parsing. This matches the behavior of strtol/strtoll and results in more
intuitive behavior.

Node type enum is not used as an array index anywhere else; the code is not
very readable and the value of this "optimization" is questionable.

The conditions are arranged so that in all normal cases the first comparison
returns true anyway.

The minneg argument is supposed to be the absolute value of the minimum negative
representable number. In case of two-complement arithmetic, it's the same as the
value itself but it's better to be explicit and negate the argument.