pegjs

History

David Majda 208cc33930 Allowed start rules must be specified explicitly Before this commit, generated parser were able to start parsing from any rule. This was nice, but it made rule code inlining impossible. Since this commit, the list of allowed start rules has to be specified explicitly using the \|allowedStartRules\| option of the \|PEG.buildParser\| method (or the --allowed-start-rule option on the command-line). These rules will be excluded from inlining when it's implemented.		2012-10-22 19:49:01 +02:00
..
compiler/passes	Merge \|allocateRegisters\| and \|computeParams\| passes	2012-07-15 17:52:03 +02:00
vendor/jasmine
generated-parser.spec.js	Allowed start rules must be specified explicitly	2012-10-22 19:49:01 +02:00
helpers.js
index.html	Merge \|allocateRegisters\| and \|computeParams\| passes	2012-07-15 17:52:03 +02:00
parser.spec.js	Change ordering of "literal", "class" and "any" code	2012-06-25 21:46:47 +02:00
README

README

PEG.js Spec Suite
=================

This is the PEG.js spec suite. It ensures PEG.js works correctly. All specs
should always pass on all supported platforms.

Running in a browser
--------------------

  1. Start a web server and make it serve the PEG.js root directory (one level
     up from this one).

  2. Point your browser to an URL corresponding to the index.html file.

  3. Watch the specs pass (or fail).

If you have Python installed, you can just run the following command in the
PEG.js root directory

  python -m SimpleHTTPServer

and load http://localhost:8000/spec/ in your browser.

Running from a command-line
---------------------------

  1. Make sure you have Node.js and the "jasmine-node" npm pacakge installed.

  2. Run the following command:

       jasmine-node --verbose .

  3. Watch the specs pass (or fail).