Obviously we don't care if examples/base64.c leaks memory before
exiting, but things like that are noise that make it hard to tell if
there's a real memory-leak problem somewhere else; it also sets a bad
example for code that someone might write modeled on the example.
This patch ensures that the example frees its allocations as it
should.

Fix segfault in base64 example with DEBUG

See merge request hammer/hammer!5

xentrac authored 5 years ago and Andrea Shepard committed 5 years ago

It was trying to dump the parse tree even when it was NULL due to parse
failure.  This was particularly a problem since earlier in the file it

Remove bogus HParser * constness and non-portable %lld format string; fixes issue 59

Closes #59

See merge request hammer/hammer!2

update to better reflect results of Great Merge and move to SC hosting

See merge request hammer/hammer!1

Add support for Python 3.x bindings

add SLOB allocator

Merging master into luajit branch

In Python 2.x an unprefixed string literal produces a byte string.
In Python 3.x an unprefixed string literal produces a textual string.

To produce a byte string in both a b prefix is needed, e.g. b'foo'.
Since I believe Hammer works predominantly with byte strings I have used
b prefixes throughout.

This removes any doubts about what type of string is in use.

This allows the library to be built and tested with a non-default
version of CPython, e.g.

scons bindings=python python=python3.6
scons bindings=python python=python3.6 testpython

In Python 3.x

- int and long types are unified. The unified type is called int.
- the text string type (unicode) is renamed to str.
- the byte string type (str) is renamed to bytes.
- chr returns a text string (i.e. str)
- xrange is renamed to range.
- dict.has_key() is removed
-

These have no effect in Python 3.x, they are the default. Enabling them
in Python 2.x, enabling them in Python 2.x allows single source
compatiblity.

Change filename in ruby bindings