0847a69643
So far, PEG.js was exported in a "PEG" global variable when no module loader was detected. The same variable name was also conventionally used when requiring it in Node.js or otherwise referring to it. This was reflected in various places in the code, documentation, examples, etc. This commit changes the variable name to "peg" and fixes all relevant occurrences. The main reason for the change is that in Node.js, modules are generally referred to by lower-case variable names, so "PEG" was sticking out when used in Node.js projects. |
9 years ago | |
---|---|---|
.. | ||
css | 15 years ago | |
json | 15 years ago | |
vendor | 9 years ago | |
README.md | 11 years ago | |
benchmarks.js | 9 years ago | |
index.css | 12 years ago | |
index.html | 9 years ago | |
index.js | 9 years ago | |
run | 9 years ago | |
runner.js | 9 years ago |
README.md
PEG.js Benchmark Suite
This is the PEG.js benchmark suite. It measures speed of the parsers generated by PEG.js on various inputs. Its main goal is to provide data for code generator optimizations.
Running in Node.js
All commands in the following steps need to be executed in PEG.js root directory (one level up from this one).
-
Install all PEG.js dependencies, including development ones:
$ npm install
-
Execute the benchmark suite:
$ make spec
-
Wait for results.
Running in the Browser
All commands in the following steps need to be executed in PEG.js root directory (one level up from this one).
-
Make sure you have Node.js and Python installed.
-
Install all PEG.js dependencies, including development ones:
$ npm install
-
Build browser version of PEG.js:
$ make browser
-
Serve PEG.js root directory using a web server:
$ python -m SimpleHTTPServer
-
Point your browser to the benchmark suite.
-
Click the Run button and wait for results.