18d266be67
Before this commit, generated parsers considered the following character sequences as newlines: Sequence Description ------------------------------ "\n" Unix "\r" Old Mac "\r\n" Windows "\u2028" line separator "\u2029" paragraph separator This commit limits the sequences only to "\n" and "\r\n". The reason is that nobody uses Unicode newlines or "\r" in practice. A positive side effect of the change is that newline-handling code became simpler (and likely faster). |
9 years ago | |
---|---|---|
.. | ||
api | 9 years ago | |
behavior | 9 years ago | |
unit | 9 years ago | |
vendor/jasmine | 11 years ago | |
.eslintrc.json | 9 years ago | |
README.md | 11 years ago | |
helpers.js | 9 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).