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
The current AASQL grammar is provided as BNF. However, most tools out there (ANTLR, Lark, ..) support EBNF which requires some transformation. It would be more straightforward to provide the grammar in EBNF form. Ideally something that is compatible with ANTLR.
The text was updated successfully, but these errors were encountered:
Usually it is better to use EBNF. First it is much shorter compared to BNF. Second, with little modification it can be compatible with grammar parsing tools out there. It is common to provide grammar in EBNF. See also XML, XPATH, and other places.
But in the end, you can some way or another, transform BNF to EBNF and make it suitable for your tooling. It is just a nice to have. Maybe you can consider this for the future iterations.
What is missing?
The current AASQL grammar is provided as BNF. However, most tools out there (ANTLR, Lark, ..) support EBNF which requires some transformation. It would be more straightforward to provide the grammar in EBNF form. Ideally something that is compatible with ANTLR.
The text was updated successfully, but these errors were encountered: