rlaemmel / yapg Goto Github PK

Currently, a few token classes are hard-wired into YAPG.
It should be possible to have new / different token classes.
It feels too expensive to fully parse lexical grammars, though.
So perhaps some sort of copy-and-paste approach could be used to include lexical grammars.
However, this is not totally obvious.
For instance, we need to map token classes to primitive types (or others).
Where would that mapping be described cheaply?

I want to keep the build process really simple and clean and thus I think that the core could remain a Makefile or I am ready to be convinced that a short, simple maven or ant file would do.

Anyway, even if we continue with Makefile, then we should download the jars from Maven repo. Is there some simple way to use maven/pom for the dependencies and have a nice classpath for a makefile?

Well, anyway, I don't mind going for maven / ant, but it is critical that the build description remains simple.

Perhaps @DerDackel or @tbernau have an opinion on that matter.

I believe it is possible to describe idiomatic grammars which are parsed, but, when mapped to Java and ANTLR, do not work as expected. So more checking should be formalized and implemented.

The generated POJO classes should also contain visitor support.
Otherwise, it is generally hard to operate on object graphs.