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
This is to remind and propose (for anyone interested) that since EBNF grammar notations/specifications do not use JSON format, but a rather similar textual format, for example
Although it is rather straightforward to transform the above examples into a JSON grammar for highlight. It is even better to have a transformation tool for that.
Given that JSON grammar (as used by *-grammar highlighter add-ons) can accept and parse EBNF/PEG notation. The task is even easier. For example, just split each rule as rule_name => rule_definition and create a JSON-like object from that (more correctly the Syntax part of the overall JSON grammar).
The text was updated successfully, but these errors were encountered:
This is to remind and propose (for anyone interested) that since
EBNF
grammar notations/specifications do not useJSON
format, but a rather similar textual format, for exampleEBNF
or even:
EBNF
Although it is rather straightforward to transform the above examples into a
JSON
grammar for highlight. It is even better to have a transformation tool for that.Given that
JSON
grammar (as used by*-grammar
highlighter add-ons) can accept and parseEBNF
/PEG
notation. The task is even easier. For example, just split each rule asrule_name => rule_definition
and create aJSON
-like object from that (more correctly theSyntax
part of the overallJSON
grammar).The text was updated successfully, but these errors were encountered: