Grammar typo
Update examples/javascript.pegjs

Changed "arguments" to "args" in several places to avoid shadowing "arguments", which is not allowed by Google Clusure Compiler.
Fix banner typo
README.md: Wrap lines at column 80
Merge pull request #113 from Almad/master

Grammar typo
Fix typo found by Almad also in the generator
Merge pull request #115 from fpirsch/patch-1

Changed "arguments" to "args" in a few places.
Do not preprecess package.json

Before this commit, package.json in the project root directory was
preprocessed in order to insert correct version into it. This made it
invalid JSON and thus unusable for npm purposes.

This commit makes package.json a valid JSON by hardcoding the version
into it. I think that introducing this small duplicity is outweighted by
being able to use npm in project root directory. For example, it is now
possible to make the "npm test" command work and introduce Travis CI
integration.
Make "npm test" work

This is will be useful for Travis CI integration
Implement Travis CI integration
Change |PEG.GrammarError| name

Change the value of the |name| property of |PEG.GrammarError| instances
from "PEG.GrammarError" to just "GrammarError". This better reflects the
fact that PEG.js can get required under different name than "PEG".
Setup prototype chain for |PEG.GrammarError| correctly
Setup prototype chain for |SyntaxError| in generated parsers correctly
Rebuild src/parser.js (forgotten in the previous commit)
Makefile: Small reordering

Define |PEGJS_VERSION| before it is used. While defining it after its
first use was OK technically, it made the code a tiny bit harder to
read.
Git repo npmization: Do not use @VERSION

When the Git repository will be a npm package, there will be no
preprocessing step and thus no @VERSION substitution. Let's get rid of
it.

Part of a fix for GH-32.
Git repo npmization: Compose PEG.js from Node.js modules

PEG.js source code becomes a set of Node.js modules that include each
other as needed. The distribution version is built by bundling these
modules together, wrapping them inside a bit of boilerplate code that
makes |module.exports| and |require| work.

Part of a fix for GH-32.
Git repo npmization: Make the repo a npm package

Includes:

  * Moving the source code from /src to /lib.
  * Adding an explicit file list to package.json
  * Updating the Makefile.
  * Updating the spec and benchmark suites and their READMEs.

Part of a fix for GH-32.
package.json: Formatting
Assume development dependencies are installed locally

This is compatible with what "npm install" does and allows for isolated
development environment.