joepie91
/
pegjs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
redux
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'efc38eef9b'
${ noResults }
pegjs/test
History
David Majda efc38eef9b Consolidate all variable name computations into one compiler pass 
Before this change, knowledge about variable names was spread between
the |computeStackDepths| pass and the code emitter code. For example,
the fact that the |&...| expression needs one variable to store a
position was represented in both places.

This changes consolidates that knowledge and introduces a new
|computeVarNames| pass. This pass replaces old |computeStackDepths|
pass, does all computations realted to variable names and stores the
results in the AST. Note that some knowledge about variables
(inevitably) remained in emitter code templates.

Beside DRYing things up, this change simplifies the emitter
significantly. By storing variable names in the AST it also allows
introduction of a pass that will identify parameters passed to actions
using proper symbol tables. Right now, this is done in a hackish way
directly in the emitter, which won't work well with changes planned in
GH-69.
 		12 years ago
..
vendor/qunit Upgrade QUnit to the current master 13 years ago
README Add command-line runner for the test suite 14 years ago
compiler-test.js Add |expected| and |found| properties to exceptions thrown by parsers 12 years ago
helpers.js Add |expected| and |found| properties to exceptions thrown by parsers 12 years ago
index.html Unify checks and passes 13 years ago
parser-test.js Fix string parsing tests 13 years ago
passes-test.js Consolidate all variable name computations into one compiler pass 12 years ago
run Use |util| module instead of |sys| 13 years ago

README 

PEG.js Test Suite
=================

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

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

  1. Open the index.html file in your browser.

  2. Watch the test pass (or fail).

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

  1. Make sure you have Node.js installed.

  2. Run the following command:

       ./run

  3. Watch the tests pass (or fail).