```
$ rebar3 shell
===> Verifying dependencies...
===> Compiling jiffy
Erlang/OTP 18 [erts-7.3] [source] [64-bit] [smp:8:8] [async-threads:0] [hipe] [kernel-poll:false]

Eshell V7.3  (abort with ^G)
1> jiffy:decode(<<"[1e310]">>).
** exception error: an error occurred when evaluating an arithmetic expression
     in function  math:pow/2
        called as math:pow(10,310)
     in call from jiffy:finish_decode/1 (jiffy/_build/default/lib/jiffy/src/jiffy.erl, line 118)
     in call from jiffy:finish_decode_arr/2 (jiffy/_build/default/lib/jiffy/src/jiffy.erl, line 149)
2> jiffy:decode(<<"[0.2e310]">>).
** exception error: bad argument
     in function  list_to_float/1
        called as list_to_float("0.2e310")
     in call from jiffy:finish_decode/1 (jiffy/_build/default/lib/jiffy/src/jiffy.erl, line 120)
     in call from jiffy:finish_decode_arr/2 (jiffy/_build/default/lib/jiffy/src/jiffy.erl, line 149)
3>
```

That `310` could depend on my machine, since `math:pow/2` says it's a limitation coming from libc.

With this change, this still throws an exception, but it doesn't come
from math or erlang, but jiffy:

```
1> jiffy:decode(<<"[1e310]">>).
** exception throw: {error,{range,310}}
     in function  jiffy:finish_decode/1 (jiffy/_build/default/lib/jiffy/src/jiffy.erl, line 121)
     in call from jiffy:finish_decode_arr/2 (jiffy/_build/default/lib/jiffy/src/jiffy.erl, line 157)
2>
```

Signed-off-by: Stephan Renatus <srenatus@chef.io>

For some reason I left a 377KiB test case checked in. Replacing this
with a generated test case is obvious in hindsight.

Windows appears to not enjoy relative path names for exectuables so
hopefully this fixes things there.

Fixes #83

Apparently hex only includes some files by default but not others
rather than a sane default of anything except for VCS directories. So
now I also get to maintain a list of files in my .app.src.

Apparently rebar3 can't generate a sane version number from Git tags and
adds a bunch of BS build number and ref tags which hex.pm then rejects.
Given that I can't find any documentation on how that works and reading
code is an exercise in over engineered abstractionism I've succumbed to
the demoralizing conclusion that I'll just have to go back to the dark
ages and maintain my versions both in source and in version control.

A call to `jiffy:encode(Term, [use_nil]).` will currently cause dialyzer
to issue a warning because `use_nil` is not included in `encode_option`.
This appears to just be an omission.

Add support for rebar3

Allow Jiffy to be used easily in projects using either rebar 2 or 3.

PropEr broke my support for R14. Turns out that EQC Mini is quite usable
so I've just switched to that. If EQC Mini exists it will be used, if
not the test is skipped gracefully.

Originally reported by @NorthNick on apache/couchdb-jiffy.

Fixed wrong jiffy:decode/2 spec

Previously if a key was malformed UTF-8 and the user specified the
`force_utf8` option we would fail to try and encode a fixed up version
of the object. This was due to missing a clause to catch the
`invalid_object_member_key` exception. This adds the clause and a couple
tests to ensure it works.

This was marked in the c_src/double-conversion directory but I've gone
ahead and added a copy to the root LICENSE file.

Time for Jiffy to enter the world of Erlang package management.

Destroy map iterators once we're done with them.

Each call to enif_map_iterator_create() must be paired with a call to
enif_map_iterator_destroy(). Otherwise, we'll leak memory.

Fixes #112

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.