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
I understand if BNF.md is supposed to be a general reference, rather than a reference of the syntax of this specific parser, but then it shouldn't be implied that it's this parser's grammar in the readme:
Covfefe/README.md
Line 64 in 8c69c03
so I assumed that this documents the version of (E)BNF this parser uses.
I see in BNF.md that Unicode scalars are supported:
Covfefe/BNF.md
Lines 182 to 184 in 8c69c03
so I tried to implement an "any non-control character goes" rule like this:
comment_char = \u{000020} ... \u{1FFFFF} ;
but I get this error message:
Error: Unmatched pattern at L1:16: '\', expected: digit | delimiting-rule-name-char | whitespace | literal | expression-optional | comment | expression-repetition | single-char-literal | delimiting-rule-name-char | expression-group
The text was updated successfully, but these errors were encountered:
Nevermind, misunderstood that these must be in a string. Whoops!
Sorry, something went wrong.
No branches or pull requests
I understand if BNF.md is supposed to be a general reference, rather than a reference of the syntax of this specific parser, but then it shouldn't be implied that it's this parser's grammar in the readme:
Covfefe/README.md
Line 64 in 8c69c03
so I assumed that this documents the version of (E)BNF this parser uses.
I see in BNF.md that Unicode scalars are supported:
Covfefe/BNF.md
Lines 182 to 184 in 8c69c03
so I tried to implement an "any non-control character goes" rule like this:
but I get this error message:
The text was updated successfully, but these errors were encountered: