Skip to content
Snippets Groups Projects
Select Git revision
  • 62f651cd909d72f203bc9bd7e88607835b082c37
  • master default protected
  • nightly_20201028
  • nightly_20201029
  • nightly_20201030
  • nightly_20201031
  • nightly_20201101
  • nightly_20201102
  • nightly_20201103
  • nightly_20201104
  • nightly_20201105
  • nightly_20201106
  • nightly_20201107
  • nightly_20201108
  • nightly_20201109
  • nightly_20201110
  • nightly_20201111
  • nightly_20201112
  • nightly_20201113
  • nightly_20201114
  • nightly_20201115
  • nightly_20201116
22 results

hammer

user avatar
"taint" memoized follow sets that came from intermediate results
Sven M. Hallberg authored 
tentative commit. this should solve issue 92, but isn't working, yet.

the idea is to taint any memoized follow set that hit a recursive loop,
directly or indirectly. the recursive calls (h_follow_rec) are allowed to use
these intermediates, but propagate the taint. the top-level routine (h_follow)
places the original taint on its result and may remove it at the end. it will
not return memoized results that are tainted (but compute them afresh).
62f651cd
History
user avatar 62f651cd
History
Name Last commit Last update
contrib
docs
examples
lib
src
testing
tools
.gitignore
.travis.yml
Doxyfile
HACKING
LICENSE
Makefile
NOTES
README.md
SConstruct
TODO
appveyor.yml
common.mk
config.mk
libhammer.pc.in
README.md

Hammer is a parsing library. Like many modern parsing libraries, it provides a parser combinator interface for writing grammars as inline domain-specific languages, but Hammer also provides a variety of parsing backends. It's also bit-oriented rather than character-oriented, making it ideal for parsing binary data such as images, network packets, audio, and executables.

Hammer is written in C, but provides bindings for other languages. If you don't see a language you're interested in on the list, just ask.

Hammer currently builds under Linux, OS X, and Windows.

Features

  • Bit-oriented -- grammars can include single-bit flags or multi-bit constructs that span character boundaries, with no hassle
  • Thread-safe, reentrant (for most purposes; see Known Issues for details)
  • Benchmarking for parsing backends -- determine empirically which backend will be most time-efficient for your grammar
  • Parsing backends:
    • Packrat parsing
    • LL(k)
    • GLR
    • LALR
    • Regular expressions
  • Language bindings:
    • C++
    • Java (incomplete)
    • Python
    • Ruby
    • Perl
    • Go
    • PHP
    • .NET
    • Lua (landing soon!)

Installing

Prerequisites

Optional Dependencies

  • pkg-config (for scons test)
  • glib-2.0 (>= 2.29) (for scons test)
  • glib-2.0-dev (for scons test)
  • swig (for Python/Perl/PHP bindings; Perl requires >= 2.0.8; Python 3.x requires >= 3.0.0)
  • python2.7-dev (for Python 2 bindings)
  • python3-dev (>= 3.5) (for Python 3 bindings)
  • a JDK (for Java bindings)
  • a working phpenv configuration (for PHP bindings)
  • Ruby >= 1.9.3 and bundler, for the Ruby bindings
  • mono-devel and mono-mcs (>= 3.0.6) (for .NET bindings)
  • nunit (for testing .NET bindings)

To build, type scons. To run the built-in test suite, type scons test. For a debug build, add --variant=debug.

To build bindings, pass a "bindings" argument to scons, e.g. scons bindings=python. scons bindings=python test will build Python bindings and run tests for both C and Python. --variant=debug is valid here too. You can build more than one set of bindings at a time; just separate them with commas, e.g. scons bindings=python,perl.

For Python, pass python=python<X>.<Y>, e. g. scons bindings=python python=python2.7 or scons bindings=python python=python3.5.

For Java, if jni.h and jni_md.h aren't already somewhere on your include path, prepend C_INCLUDE_PATH=/path/to/jdk/include to that.

To make Hammer available system-wide, use scons install. This places include files in /usr/local/include/hammer and library files in /usr/local/lib by default; to install elsewhere, add a prefix=<destination> argument, e.g. scons install prefix=$HOME. A suitable bindings= argument will install bindings in whatever place your system thinks is appropriate.

Usage

Just #include <hammer/hammer.h> (also #include <hammer/glue.h> if you plan to use any of the convenience macros) and link with -lhammer.

If you've installed Hammer system-wide, you can use pkg-config in the usual way.

To learn about hammer check

Examples

The examples/ directory contains some simple examples, currently including:

Known Issues

The Python bindings work with Python 2.7, and Python 3.5+.

The requirement for SWIG >= 2.0.8 for Perl bindings is due to a known bug in SWIG. ppa:dns/irc has backports of SWIG 2.0.8 for Ubuntu versions 10.04-12.10; you can also build SWIG from source.

The .NET bindings are for Mono 3.0.6 and greater. If you're on a Debian-based distro that only provides Mono 2 (e.g., Ubuntu 12.04), there are backports for 3.0.x, and a 3.2.x PPA maintained by the Mono team.

The regular expression backend is potentially not thread-safe (thanks to Martin Murray for pointing this out). A full rewrite of this backend is on the roadmap already due to some unexpected nondeterminism in the current implementation; we plan to fix this problem in that rewrite.

Community

Mailing list, IRC, and potentially other channels to come.

Contact

Also to be updated soon.