You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature Request: Configurable "equality" symbol in production rule #29
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.
changed the title [-]Configurable "equality" symbol in production rule[/-][+]Feature Request: Configurable "equality" symbol in production rule[/+]on Sep 18, 2020
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?
Activity
[-]Configurable "equality" symbol in production rule[/-][+]Feature Request: Configurable "equality" symbol in production rule[/+]katef commentedon Sep 20, 2020
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?
mingodad commentedon Mar 24, 2021
Look here for how this project seems to manage configuration: https://github.com/gotthardp/bnfparser2/tree/master/parser/share/syntax
mingodad commentedon Mar 25, 2021
Also would be nice if
kgtcould support theEBNFsupported by https://www.bottlecaps.de/rr/ui I did converted several (64) grammars to it here https://github.com/mingodad/plgh and would like to have then been managed bykgt