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

[Scott Stanchfield]

I don't think we'd need a separate code generator (unless we want to do
something radical); just an option for generating 1.5 code. It shouldn't
affect much in the JavaCodeGenerator.

If I have a chance, I'll take a peek since I'm doing a lot of work on the
JavaCodeGenerator for source-line mapping anyway...

Later,
-- Scott

> -----Original Message-----
> From: antlr-interest-bounces at antlr.org 
> [mailto:antlr-interest-bounces at antlr.org] On Behalf Of Prashant Deva
> Sent: Tuesday, February 22, 2005 8:12 PM
> To: antlr-interest at antlr.org
> Subject: Re: [antlr-interest] How about migrating java 
> generated code to java 5
> 
> 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
> > >
> >
>