You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
David Majda e8be76ee3a Don't expose the "parser" variable in parser code
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.
8 years ago
..
compiler Don't expose the "parser" variable in parser code 8 years ago
utils Remove trailing commas in object literals 9 years ago
.eslintrc.json ESLint: Set environments better 8 years ago
grammar-error.js Merge pull request #347 from mbaumgartl/errorstack 9 years ago
parser.js Construct expectations using functions 8 years ago
peg.js Don't use "this" inside peg.generate 8 years ago