__color__,ticket,summary,component,version,milestone,type,owner,status,created,_changetime,_description,_reporter 3,1,bnfc -ocaml silently ignores token definitions,OCaml back-end,,,defect,somebody,new,2008-06-11T12:59:50Z+0100,2008-07-08T08:00:52Z+0100,"When running ""bnfc -ocaml"", bnfc silently ignores 'token' definitions. Reproduced with latest darcs.",andre 1,5,bnfc demo fails to build on Java 1.6,Java back-end,,None,enhancement,,new,2008-08-21T13:51:13Z+0100,2008-08-21T13:51:13Z+0100,"Looking at bnfc, I tried the 'make' the calc.cf example. Fails on multiple errors. Shown below. regards javac -sourcepath . calc/Absyn/Exp.java calc/Absyn/EAdd.java calc/Absyn/ESub.java calc/Absyn/EMul.java calc/Absyn/EDiv.java calc/Absyn/EInt.java ---------- 1. ERROR in calc/Absyn/Exp.java (at line 4) public abstract R accept(Exp.Visitor v, A arg); ^^^ Syntax error, type parameters are only available if source level is 5.0 ---------- 2. ERROR in calc/Absyn/Exp.java (at line 4) public abstract R accept(Exp.Visitor v, A arg); ^ R cannot be resolved to a type ---------- 3. ERROR in calc/Absyn/Exp.java (at line 4) public abstract R accept(Exp.Visitor v, A arg); ^^^ Syntax error, parameterized types are only available if source level is 5.0 ---------- 4. ERROR in calc/Absyn/Exp.java (at line 4) public abstract R accept(Exp.Visitor v, A arg); ^ R cannot be resolved to a type ---------- 5. ERROR in calc/Absyn/Exp.java (at line 4) public abstract R accept(Exp.Visitor v, A arg); ^ A cannot be resolved to a type ---------- 6. ERROR in calc/Absyn/Exp.java (at line 4) public abstract R accept(Exp.Visitor v, A arg); ^ A cannot be resolved to a type ---------- 7. ERROR in calc/Absyn/Exp.java (at line 5) public interface Visitor { ^^^ Syntax error, type parameters are only available if source level is 5.0 ---------- 8. ERROR in calc/Absyn/Exp.java (at line 6) public R visit(calc.Absyn.EAdd p, A arg); ^ R cannot be resolved to a type ---------- 9. ERROR in calc/Absyn/Exp.java (at line 6) public R visit(calc.Absyn.EAdd p, A arg); ^ A cannot be resolved to a type ---------- 10. ERROR in calc/Absyn/Exp.java (at line 7) public R visit(calc.Absyn.ESub p, A arg); ^ R cannot be resolved to a type ---------- 11. ERROR in calc/Absyn/Exp.java (at line 7) public R visit(calc.Absyn.ESub p, A arg); ^ A cannot be resolved to a type ---------- 12. ERROR in calc/Absyn/Exp.java (at line 8) public R visit(calc.Absyn.EMul p, A arg); ^ R cannot be resolved to a type ---------- 13. ERROR in calc/Absyn/Exp.java (at line 8) public R visit(calc.Absyn.EMul p, A arg); ^ A cannot be resolved to a type ---------- 14. ERROR in calc/Absyn/Exp.java (at line 9) public R visit(calc.Absyn.EDiv p, A arg); ^ R cannot be resolved to a type ---------- 15. ERROR in calc/Absyn/Exp.java (at line 9) public R visit(calc.Absyn.EDiv p, A arg); ^ A cannot be resolved to a type ---------- 16. ERROR in calc/Absyn/Exp.java (at line 10) public R visit(calc.Absyn.EInt p, A arg); ^ R cannot be resolved to a type ---------- 17. ERROR in calc/Absyn/Exp.java (at line 10) public R visit(calc.Absyn.EInt p, A arg); ^ A cannot be resolved to a type ---------- ---------- 18. ERROR in calc/Absyn/EAdd.java (at line 8) public R accept(calc.Absyn.Exp.Visitor v, A arg) { return v.visit(this, arg); } ^^^ Syntax error, type parameters are only available if source level is 5.0 ---------- 19. ERROR in calc/Absyn/EAdd.java (at line 8) public R accept(calc.Absyn.Exp.Visitor v, A arg) { return v.visit(this, arg); } ^^^ Syntax error, parameterized types are only available if source level is 5.0 ---------- ---------- 20. ERROR in calc/Absyn/ESub.java (at line 8) public R accept(calc.Absyn.Exp.Visitor v, A arg) { return v.visit(this, arg); } ^^^ Syntax error, type parameters are only available if source level is 5.0 ---------- 21. ERROR in calc/Absyn/ESub.java (at line 8) public R accept(calc.Absyn.Exp.Visitor v, A arg) { return v.visit(this, arg); } ^^^ Syntax error, parameterized types are only available if source level is 5.0 ---------- ---------- 22. ERROR in calc/Absyn/EMul.java (at line 8) public R accept(calc.Absyn.Exp.Visitor v, A arg) { return v.visit(this, arg); } ^^^ Syntax error, type parameters are only available if source level is 5.0 ---------- 23. ERROR in calc/Absyn/EMul.java (at line 8) public R accept(calc.Absyn.Exp.Visitor v, A arg) { return v.visit(this, arg); } ^^^ Syntax error, parameterized types are only available if source level is 5.0 ---------- ---------- 24. ERROR in calc/Absyn/EDiv.java (at line 8) public R accept(calc.Absyn.Exp.Visitor v, A arg) { return v.visit(this, arg); } ^^^ Syntax error, type parameters are only available if source level is 5.0 ---------- 25. ERROR in calc/Absyn/EDiv.java (at line 8) public R accept(calc.Absyn.Exp.Visitor v, A arg) { return v.visit(this, arg); } ^^^ Syntax error, parameterized types are only available if source level is 5.0 ---------- ---------- 26. ERROR in calc/Absyn/EInt.java (at line 8) public R accept(calc.Absyn.Exp.Visitor v, A arg) { return v.visit(this, arg); } ^^^ Syntax error, type parameters are only available if source level is 5.0 ---------- 27. ERROR in calc/Absyn/EInt.java (at line 8) public R accept(calc.Absyn.Exp.Visitor v, A arg) { return v.visit(this, arg); } ^^^ Syntax error, parameterized types are only available if source level is 5.0 ",dpawson 3,2,C++ etc cannot handle single quotes,C++ back-end,2.4b,None,defect,,new,2008-07-08T08:02:14Z+0100,2008-07-08T08:10:12Z+0100,"bnfc in -c, -cpp , -cpp_std etc. modes cannot handle single aphostropes {{{\'}}} Either the .l and .y files will contain {{{\\'}}} (not desired) or Parser.c will contain {{{'''}}} (syntax error). ",gazso@… 4,4,Empty tokens produce invalid lexer specifications,Not back-end specific,,None,defect,,new,2008-07-08T08:21:33Z+0100,2008-07-08T08:21:33Z+0100,"If there are empty tokens in the LBNF file, several of the back-ends produce invalid lexer specifications. For example: {{{ F. C ::= """" ; G. C ::= ""foo"" ; }}} At least the generated Alex and JLex code for this is invalid. BNFC should consider empty tokens to be errors, or possibly silently convert them to empty tokens lists. This issue was first reported by didier.garcin@club-internet.fr",bringert 4,6,Generate Emacs mode,Not back-end specific,,None,enhancement,,new,2008-11-04T07:59:58Z+0000,2008-11-04T07:59:58Z+0000,"On Tue, Nov 4, 2008 at 7:51 AM, Peter White wrote: > A feature suggestion for BNFC: Have it also generate an emacs-mode for the > language. > Thanks for the useful tool.",bringert 4,3,Happy GLR back-end uses FiniteMap,Haskell back-end,2.4b,None,defect,,new,2008-07-08T08:06:24Z+0100,2008-07-08T08:07:42Z+0100,"I intend to build an Ada 2005 parser for fun, first and probably to automaticly generate C and C++ bindings for Ada and certainly others projects if I succeed. I have been seduced by BNF Converter to do this job. I'm yet really familar with Haskell but I have motivation enough to learn. In fact, I have some trouble to compile generated Haskell code from BNFC. It seems BNFC, designed to operate in collaboration with an old Data library because a FiniteMap import appears in generated code. But FiniteMap is now obsolete and it doesn't seem having a corresponding Data Type in Haskell 6 even not Data.Map. So, what is the procedure to adopt in order to build Test executable ? Is there a round-trip ? ",didier.garcin@…