-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Feature Request: Configurable "equality" symbol in production rule #29
Comments
I wonder if it would make sense to attempt to provide a "generic" BNF dialect, where this (and #28 and other aspects) are configurable. This might be enough to deal with W3C, lua, the C standard and a few other "casual" dialects. The only dialects implemented currently are standardised ones - that is, formally specified by a particular standards body. I've resisted adding an add-hoc dialect, because of course everybody writes theirs differently. Details like escapes within strings get difficult. But I can imagine exposing a bunch of settings like this. Maybe the syntax is fixed, but the lexing is configurable? |
Look here for how this project seems to manage configuration: https://github.com/gotthardp/bnfparser2/tree/master/parser/share/syntax |
Also would be nice if
|
Many grammars use different equality symbols to separate the left and right sides of a production rule:
symbol ::= replacement
symbol = replacement
symbol → replacement
If this symbol was configurable, it would make it easier to use these grammars with the tool.
The text was updated successfully, but these errors were encountered: