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.
4.4 KiB
4.4 KiB
editLink |
---|
false |
See commit history for a full list of changes.
v0.8.0 (December 24, 2013)
Big Changes
- Completely rewrote the code generator. Among other things, it allows optimizing generated parsers for parsing speed or code size using the
optimize
option of thePEG.buildParser
method or the--optimize
/-o
option on the command-line. All internal identifiers in generated code now also have apeg$
prefix to discourage their use and avoid conflicts. [#35, #92] - Completely redesigned error handling. Instead of returning
null
inside actions to indicate match failure, newexpected
anderror
functions can be called to trigger an error. Also, expectation inside theSyntaxError
exceptions are now structured to allow easier machine processing. [#198] - Implemented a plugin API. The list of plugins to use can be specified using the
plugins
option of thePEG.buildParser
method or the--plugin
option on the command-line. Also implemented the--extra-options
and--extra-options-file
command-line options, which are mainly useful to pass additional options to plugins. [#106] - Made
offset
,line
andcolumn
functions, not variables. They are now available in all parsers and return lazily-computed position data. Removed now uselesstrackLineAndColumn
option of thePEG.buildParser
method and the--track-line-and-column
option on the command-line. - Added a new
text
function. When called inside an action, it returns the text matched by action's expression. [#131] - Added a new
$
operator. It extracts matched strings from expressions. - The
?
operator now returnsnull
on unsuccessful match. - Predicates now always return
undefined
. - Replaced the
startRule
parameter of theparse
method in generated parsers with more genericoptions
parameter. The start rule can now be specified as thestartRule
option. Theoptions
parameter can be also used to pass custom options to the parser because it is visible as theoptions
variable inside parser code. [#37] - The list of allowed start rules of a generated parser now has to be specified explicitly using the
allowedStartRules
option of thePEG.buildParser
method or the--allowed-start-rule
option on the command-line. This will make certain optimizations like rule inlining easier in the future. - Removed the
toSource
method of generated parsers and introduced a newoutput
option of thePEG.buildParser
method. It allows callers to specify whether they want to get back the parser object or its source code. - The source code is now a valid npm package. This makes using development versions easier. [#32]
- Generated parsers are now ~25% faster and ~62%/~3% smaller (when optimized for size/speed) than those generated by 0.7.0.
- Requires Node.js 0.8.0+.
Small Changes
bin/pegjs
now outputs just the parser source if the value of the--export-var
option is empty. This makes embedding generated parsers into other files easier. [#143]- Changed the value of the
name
property ofPEG.GrammarError
instances from “PEG.GrammarError” to just “GrammarError”. This better reflects the fact that PEG.js can get required with different variable name thanPEG
. - Setup prototype chain for
PEG.GrammarError
correctly. - Setup prototype chain for
SyntaxError
in generated parsers correctly. - Fixed error messages in certain cases with trailing input [#119]
- Fixed code generated for classes starting with
\^
. [#125] - Fixed too eager proxy rules removal. [#137]
- Added a license to all vendored libraries. [#207]
- Converted the test suite from QUnit to Jasmine, cleaning it up on the way.
- Travis CI integration.
- Various internal code improvements and fixes.
- Various generated code improvements and fixes.
- Various example grammar improvements and fixes.
- Improved
README.md
. - Converted
CHANGELOG
to Markdown.