-
The following LBNF generates bad haskell code with a few weird `p[Expr]`s.
```
comment "//";
comment "/*" "*/";
separator Expr ",";
coercions Expr 3;
ExprAdd. Expr ::= Expr "+" E…
-
Recover the property of BNFC 2.7.1 to generate warning-free Haskell code
https://github.com/BNFC/bnfc/blame/0ad87322fce4cfe309512fa9fd56a63a06ff9c19/source/CHANGELOG.md#L117
- [x] `Abs.hs`: unused…
-
I use doctest in a test-suite, set-up in cabal like this:
``` cabal
Test-suite bnfc-doctests
type: exitcode-stdio-1.0
ghc-options: -threaded
main-is: doctests.hs
b…
-
The `*.y` template file generated by BNFC using global varilables to store the parsed AST and internal status.
```c
/* Global variables holding parse results for entrypoints. */
Proc YY_RESULT_Pr…
-
BNFC version 2.9.1
Here is the code generated by BNFC
```c
/* Entrypoint: parse Proc from string. */
Proc psProc(const char *str)
{
YY_BUFFER_STATE buf;
mylang__init_lexer(0);
buf = …
-
BNFC release 2.8, and up to the latest commit.
The Java backend is sensitive to the order of the macros/productions.
For instance the following gives errors, both using CUP and ANTLR4:
```
separator …
gapag updated
3 years ago
-
It seems that the generated C parser doesn't like it when using an entry point which is not the first category:
```
entrypoints Bar;
F. Foo ::= "foo" ;
B. Bar ::= "bar" ;
```
```
$ bnfc -c -m Test.c…
-
I tried to use HTF with ghc 8.8 and cabal on travis, but it failed (see https://travis-ci.org/BNFC/bnfc/jobs/622005387 ):
```
trying: HTF-0.14.0.1 (dependency of bnfc-system-tests-0.1.1.0)
next goa…
-
See #163 and https://github.com/antlr/antlr4/issues/2689 : ANTLR will sometimes require a start rule
```
StartX : X EOF;
```
for entrypoint `X`. The current ANTLR backend does not emit such sta…
-
When generating a .y file with the `--glr` flag enabled, the .y header gets a `-- module name filled in by Happy` line written. This makes happy (I'm using version 1.19.9) spit out a file with incorre…