pegjs/lib/grammar-error.js

var classes = require("./utils/classes");

/* Thrown when the grammar contains an error. */
function GrammarError(message) {
  this.name = "GrammarError";
  this.message = message;
}

classes.subclass(GrammarError, Error);

module.exports = GrammarError;
Utility functions cleanup: Split lib/utils.js Split lib/utils.js into multiple files. Some of the functions were generic, these were moved into files in lib/utils. Other funtions were specific for the compiler, these were moved to files in lib/compiler. This commit only moves functions around -- there is no renaming and cleanup performed. Both will come later. 2014-05-08 11:48:56 +02:00			`var classes = require("./utils/classes");`
Git repo npmization: Compose PEG.js from Node.js modules PEG.js source code becomes a set of Node.js modules that include each other as needed. The distribution version is built by bundling these modules together, wrapping them inside a bit of boilerplate code that makes \|module.exports\| and \|require\| work. Part of a fix for GH-32. 2012-11-10 09:47:22 +01:00
			`/* Thrown when the grammar contains an error. */`
Change module exporting style Modules now generally store the exported object in a named variable or function first and only assign \|module.exports\| at the very end. This is a difference when compared to style used until now, where most modules started with a \|module.exports\| assignment. I think the explicit name helps readability and understandability. 2014-05-04 14:11:44 +02:00			`function GrammarError(message) {`
Git repo npmization: Compose PEG.js from Node.js modules PEG.js source code becomes a set of Node.js modules that include each other as needed. The distribution version is built by bundling these modules together, wrapping them inside a bit of boilerplate code that makes \|module.exports\| and \|require\| work. Part of a fix for GH-32. 2012-11-10 09:47:22 +01:00			`this.name = "GrammarError";`
			`this.message = message;`
Change module exporting style Modules now generally store the exported object in a named variable or function first and only assign \|module.exports\| at the very end. This is a difference when compared to style used until now, where most modules started with a \|module.exports\| assignment. I think the explicit name helps readability and understandability. 2014-05-04 14:11:44 +02:00			`}`
Git repo npmization: Compose PEG.js from Node.js modules PEG.js source code becomes a set of Node.js modules that include each other as needed. The distribution version is built by bundling these modules together, wrapping them inside a bit of boilerplate code that makes \|module.exports\| and \|require\| work. Part of a fix for GH-32. 2012-11-10 09:47:22 +01:00
Utility functions cleanup: Split lib/utils.js Split lib/utils.js into multiple files. Some of the functions were generic, these were moved into files in lib/utils. Other funtions were specific for the compiler, these were moved to files in lib/compiler. This commit only moves functions around -- there is no renaming and cleanup performed. Both will come later. 2014-05-08 11:48:56 +02:00			`classes.subclass(GrammarError, Error);`
Change module exporting style Modules now generally store the exported object in a named variable or function first and only assign \|module.exports\| at the very end. This is a difference when compared to style used until now, where most modules started with a \|module.exports\| assignment. I think the explicit name helps readability and understandability. 2014-05-04 14:11:44 +02:00
			`module.exports = GrammarError;`