[antlr-interest] How about migrating java generated code to java 5

Prashant Deva prashant.deva at gmail.com
Tue Feb 22 17:12:25 PST 2005


Well, i guess we will need to have a separate generator for pre 1.5 java.
But we would HAVE to move ultimately to java 1.5 code. Maybe instead
of putting it in any of 2.xx releases, it would be better to have only
1.5 support in antlr3 , with no support for pre 1.5.
As antlr 3 will already have a bunch of radical changes, the complete
shift to java 5 generated code shouldn't do any harm.

PRASHANT

On Tue, 22 Feb 2005 17:09:54 -0500, Bryan Ewbank <ewbank at gmail.com> wrote:
> Would this clobber pre-1.5 support?
> 
> 
> On Tue, 22 Feb 2005 20:00:54 +0530, Prashant Deva
> <prashant.deva at gmail.com> wrote:
> > I get a whole bunch of warnings in eclipse 3.1 for the antlr generated
> > files not being java 5 compliant. So how about changing the code
> > generator so that it can generate java 1.5 compliant code?
> >
> > It would provide much better type safety in our programs, for instance
> > , if the token types were kept in an enum instead of an interface
> > definition.
> >
> > PRASHANT
> >
>


More information about the antlr-interest mailing list