When building a c++ parser with the javaccPlugin, the compilejJtree does not take into account the user's defined AST node that can be used by the generated grammar. IMO, this is because the c++ source code organization does not follow the implicit rules that exists on the Java side. thus adding a new option as below would help the compileJjtree task to not override/generate the user's defined AST.
Hi John
When building a c++ parser with the javaccPlugin, the compilejJtree does not take into account the user's defined AST node that can be used by the generated grammar. IMO, this is because the c++ source code organization does not follow the implicit rules that exists on the Java side. thus adding a new option as below would help the compileJjtree task to not override/generate the user's defined AST.
There is a user's case here https://github.com/jtb-javacc/EGC. The EG1 generation is ok, while the EG2, EG3, EG4 are not ok.