Optional Semicolons about bnfc

[andreasabel]

There is work in progress by @beataburreau on a new implementation of BNFC where one has a newline special token.

[andreasabel]

@praduca: There is same hard-writing in the render function of the generated printer biased towards "braces and semicolon" style languages. If you want some other rendering, you have to patch the generated printer.

[praduca]

Ah good to know it is something simple. Thanks for commenting so quickly

[ScottFreeCode]

This is clearly not a dealbreaker, I could go with mandatory semicolons or figure out a way to use layout even if that seems opinionated.

But – the fact that the "\n" seems to be getting translated into the same thing as "" i.e. some whitepsace separation required but can be any space and prints as a single space, rather than either:

• actually requiring and printing the specified character, or else
• choking and saying "Don't include whitespace in your tokens!!"

…seems like a bug. Having the character I explicitly specified be accepted but treated as other characters, is definitely unexpected (or at least unintuitive) behavior.

[praduca]

I think there is some bug about using semicolons somewhere... I'm trying to make a tinybasic grammar, but when i use a semicolon as a separator (like "PRINT A$;B$" ) it parses ok but the prettyprinter put every part on a different line. Changing the separator to a comma works fine...