-
Notifications
You must be signed in to change notification settings - Fork 9
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
No strings #16
Comments
@macmodrov Well, we can add strings support as an optional feature. So that, users will able to configure symbols recognized by mode as a valid set. What do you think about this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This mode does not treat quoted strings as strings. I am aware this is on purpose:
All resources I could find about pure BNF (as opposed to EBNF and ABNF) show quoted strings.
This decision prevents specifying terminals as strings, especially strings containing a semicolon (unless escaped with a backslash as
"\;"
).I believe double quoted strings should be restored.
The text was updated successfully, but these errors were encountered: