-
Notifications
You must be signed in to change notification settings - Fork 6
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
BNF comments not supported #2
Comments
Originally, I excluded |
Actually, EBNF allows multiple rules per line, separated by a semicolon. EBNF and BNF syntaxes are not very compatible. I think, in the long run, it's better to create two separate languages in the extension. |
After reading more about BNF, I guess there is not much of a specification, contrary to EBNF. Every source has its own variants and extensions and presents it as "the BNF". As such, I guess support for BNF should not be the top priority. I switched to EBNF for my project, anyway. |
Makes sense, but honestly never tried that, so I don't even know if the extension currently supports that. All in all, I guess it would be best to just leave it be as is? Maybe in the future add an option to be able to toggle between BNF and EBNF, but that's beyond what I currently have time for. I'll leave the issue open. |
According to specification, a comment in a BNF file starts with a semicolon (
;
) and extends to the end of the line.This extension supports only line comments starting with
#
and block comments between(*
and*)
. The latter is EBNF-style comment, the former is not copatible with neither BNF, EBNF or ABNF.The text was updated successfully, but these errors were encountered: