da2378d887
Instead of testing arguments.length to see whether an optional parameter was passed to a function, compare its value to "undefined". This approach has two advantages: * It is in line with handling of default parameters in ES6. * Optional parameters are actually spelled out in the parameter list. There is also one important disadvantage, namely that it's impossible to pass "undefined" as an optional parameter value. This required a small change in two tests. Additional notes: * Default parameter values are set in assignments immediately after the function header. This reflects the fact that these assignments really belong to the parameter list (which is where they are in ES6). * Parameter values are checked against "void 0" in places where "undefined" can potentially be redefiend. |
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).