pegjs

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.

History

David Majda 25ab98027d Remove info about found string from syntax errors The \|found\| property wasn't very useful as it mostly contained just one character or \|null\| (the exception being syntax errors triggered by \|error\| or \|expected\|). Similarly, the "but XXX found" part of the error message (based on the \|found\| property) wasn't much useful and was redundant in presence of location info. For these reasons, this commit removes the \|found\| property and corresponding part of the error message from syntax errors. It also modifies error location info slightly to cover a range of 0 characters, not 1 character (except when the error is triggered by \|error\| or \|expected\|). This corresponds more precisely to the actual situation. Fixes #372.	9 years ago
..
generated-parser-behavior.spec.js	Remove info about found string from syntax errors	9 years ago

David Majda 25ab98027d Remove info about found string from syntax errors

The |found| property wasn't very useful as it mostly contained just one
character or |null| (the exception being syntax errors triggered by
|error| or |expected|). Similarly, the "but XXX found" part of the error
message (based on the |found| property) wasn't much useful and was
redundant in presence of location info.

For these reasons, this commit removes the |found| property and
corresponding part of the error message from syntax errors. It also
modifies error location info slightly to cover a range of 0 characters,
not 1 character (except when the error is triggered by |error| or
|expected|). This corresponds more precisely to the actual situation.

Fixes #372.

generated-parser-behavior.spec.js

Remove info about found string from syntax errors