Andreas Abel

A more general solution is #267.

Yes, one could modify `Setup.lhs` to include code that generates the LBNF parser from the `BNF.cf` file, using BNFC. Currently Setup is the default script: https://github.com/BNFC/bnfc/blob/fb85ff110f11390588a2522588a6c0083b03ad57/source/Setup.lhs#L1-L6 However, I don't see...

@peti, I agree that it would be nicer if Cabal would know about the BNFC-generated files. I did some research but did not find out how to teach Cabal about...

So a first step could be to have the Haskell backend of BNFC generate a `Setup.hs` script that does the correct invocation of BNFC. Once the logic has been found...

See also this discussion on adding BNFC support to cabal: https://github.com/haskell/cabal/issues/6726

@peti wrote: > Checking generating source code into the git repository, however, is a really bad idea because people will forget to update those files. If you use a front-end...

Hello @shlevy, thanks for your initiative! Atm, there is no such documentation, but I can summarize the most important steps for a new backend: 1. a new `Target` in `Options.hs`:...

@shlevy Great! We decided here locally that it is better to place new backends in BNFC 2.x still (meaning here), to not put pressure on the BNFC-3 development process. The...

The C/Java backends (?Lex) did not support more than one block comment form. This has been fixed now by introducing different start conditions COMMENT, COMMENT1, ... for different block comment...

For Haskell/Java, I implemented in 83681fa9893728e35277fe9987a6950fc3851573 a translation from block comment terminator strings to regular expressions that works correctly for C-style comments `/* ... */` and HTML-style comments ``. (The...