e8be76ee3a
The "parser" variable allowed access to the parser object. Among other
things, this made it possible to invoke the parser recursively using
"parser.parse".
One problem with the "parser" variable is that it bakes in the idea that
the parser is an *object*, not a *module*. While this is true now, it
won't necessarily be in the future, when parsers may be exported as ES6
modules. Also, people tend to use parsers as modules even today, e.g.
like this:
var parse = require("parser").parse;
var result = parse(...);
Such usage broke the "parser" variable (as it was implemented).
For this reasons I decided to remove the "parser" variable. If someone
needs to do tricks like recursive invocation of the parser, he/she must
pass the parser or the "parse" function itself using options.
Related to #433.
|
||
|---|---|---|
| .. | ||
| api | ||
| behavior | ||
| unit | ||
| vendor/jasmine | ||
| .eslintrc.json | ||
| helpers.js | ||
| index.html | ||
| 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 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:
$ node_modules/.bin/http-server -
Point your browser to the spec suite.
-
Watch the specs pass (or fail).