We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For example take the grammar
predicate = (!"b" .)+
with the input b, it will output the wrong message:
b
unexpected `b`, expecting .
Other example could be find as well, this is because when logging errors we do not know we under in a not predicate.
The text was updated successfully, but these errors were encountered:
This is described more in depth in:
Maidl, André Murbach, Sérgio Medeiros, Fabio Mascarenhas, and Roberto Ierusalimschy. “Error Reporting in Parsing Expression Grammars.” arXiv Preprint arXiv:1405.6646, 2014. http://arxiv.org/abs/1405.6646.
The strategy is quite simple, just ignore errors inside !p, and blame any failure on !p itself. From the example above we could obtain
!p
unexpected `b`, expecting `!"b"`.
in a first time even if it could be improved later.
Sorry, something went wrong.
No branches or pull requests
For example take the grammar
with the input
b
, it will output the wrong message:Other example could be find as well, this is because when logging errors we do not know we under in a not predicate.
The text was updated successfully, but these errors were encountered: