rebar.config: set CFLAGS/CXXFLAGS/LDFLAGS on Hurd

The environment variable approach breaks other projects' Travis-CI runs
if they include other projects that depend on a different version of
PropEr.

Fixes: #106

Use the common CFLAGS/CXXFLAGS/LDFLAGS used on Linux/FreeBSD/etc also
on GNU/Hurd.

Fix win32 build

This test has proved its point and now just exists to randomly fail some
builds depending on race conditions with the garbage collector.

I was being lazy and relying on Travis. This fixes up the map spec for
newer VMs.

This obviously only exists on VMs that support it.

In the original PR for `return_trailer` @vlm pointed out that I wasn't
using enif_consume_timeslice correctly. This fixes that by changing out
its called.

Previously we attempted to define the total number of bytes to decode or
encode in a single NIF call and then would consume as much of the
timeslice as we processed. This is wrong because we may start the NIF
call with less than an entire timeslice left.

The new approach is to define the number of bytes to encode or decode
per reduction and then iteratively call enif_consume_timeslice until it
indicates that we should return.

Previously Jiffy would throw an error about trailing data if there is
any non-whitespace character encounter after the first term had been
decoded.

This patch adds a decoder option `return_trailer` that will instead
return a sub-binary starting at the first non-whitespace character. This
allows users to be able to decode multiple terms from a single iodata()
term.

Thanks to @vlm for the original patch.

Add compile option no_native

Thanks to @joedevivo for the contribution.

Fixes #85

Thanks to @dvliman and @kxepal for noticing.

Add replace_undefined and escape_forward_slashes

This brings back escaping forward slashes as an option during encoding.
Default is still not to escape.

This is pretty much a generalisation of the use_nil option to support an
arbitrary atom.

Changed pos to unsigned int to prevent warning from happening.

update README.md fixing typo in maps example

rebar.config: fix Windows support (CFLAGS, CXXFLAGS)

This sounds rather insane to me but I've managed to show that `(char)
-1` is converted to 255 on some platforms. This was reproduced on
ppc64el via Qemu on OS X. A simple program that does `fprintf(stderr,
"%d\r\n", (char) -1);` prints 255 to the console. Rather than rely on
the signedness of a char I've just updated things to use an unsigned
char (which hopefully is never signed) and replaced -1 with 255 for the
sentinel value when converting hex values.

Thanks to Balint Reczey (@rbalint) for the report.

Fixes #74

This fixes a leak when encoding a bare bignum. Technically it would be
possible to hit this memory leak randomly with bignums in objects but
the chances are highly unlikely.

Thanks to @miriampena for the issue.

Fixes #69

The `val` variable is a register value that we need to be able to return
at any time from `decode_iter`. If it happened that a yield was
triggered while processing trailing whitespace the lack of persistance
caused decode to return a term intialized from a random integer value.
Obviously the Erlang VM did not enjoy this.

Thanks to @michalpalka for the report.

Fixes #66

This updates encoder errors to report the actual Erlang value that
caused the error. This should make it easier to debug errors when
generating JSON.

I must've managed to miss the PR update from Stanislav the other day
when merging this.

This implements the `use_nil` option as discussed on issue #64. Passing
the atom `use_nil` as an option to both encode and decode will replace
the atom `null` with `nil` when decoding and encode `nil` as `null` when
encoding values.

Fixes #64
Fixes #68

Rather than worry about truncation casting from a possibly 64bit value
down to a possibly 32bit size_t we just limit the total bytes per
invocation to 4G using an unsigned integer.

Thanks to @seriyps for the report.

Fixes #61

This is motivated by issue #60 to see if we can get away with `-O3`
while still handling the cast of a `Decoder**` to `void**`.

Fixes #60

Timeouts apparently don't actually work unless you use a test generator.
Which makes sense in hindsight.