-
-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
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
Document Lexer Rules #24
Comments
Can you provide an example? |
Also, have you tried latest master? I just merged the lookahead branch which should since this. |
Sorry, was on mobile. I assume you're talking about the EBNF lexer. Can you provide the full lexer you're using that breaks, and an example grammar that fails? (your example above is missing the definition for |
Just me being a noob very sorry |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Depending on the lexiconal order the EBNF rules, what is and is not a valid parse changes.
Now to a degree this makes sense, but most implementations resolve this ahead of time.
But for example if I have an EBNF like
(
.
changed to;
for github syntax highlighting)This will correctly parse for
@Version
and@PackageID
But if I add the rule:
Anything tagged as
@PackageID
breaks because it doesn't contain a:
character.The text was updated successfully, but these errors were encountered: