25ab98027d
The |found| property wasn't very useful as it mostly contained just one character or |null| (the exception being syntax errors triggered by |error| or |expected|). Similarly, the "but XXX found" part of the error message (based on the |found| property) wasn't much useful and was redundant in presence of location info. For these reasons, this commit removes the |found| property and corresponding part of the error message from syntax errors. It also modifies error location info slightly to cover a range of 0 characters, not 1 character (except when the error is triggered by |error| or |expected|). This corresponds more precisely to the actual situation. Fixes #372. |
9 years ago | |
---|---|---|
.. | ||
api | 9 years ago | |
behavior | 9 years ago | |
unit | 9 years ago | |
vendor/jasmine | 11 years ago | |
README.md | 11 years ago | |
helpers.js | 10 years ago | |
index.html | 9 years ago |
README.md
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 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 spec suite:
$ make spec
-
Watch the specs pass (or fail).
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 spec suite.
-
Watch the specs pass (or fail).