Re: Re: generics in ASM

Eugene,

If you do decide to generify ASM, I might be interested in contributing to
the conversion process - it would be a good way to learn a little more about
the internals of ASM.

Regards,
Joshua

On Wed, Jul 21, 2010 at 8:38 AM, Eugene Kuleshov <[email protected]>wrote:

> Joshua,
>
>  ASM never been generified. The main reason is to maintain
> compatibility with Java 1.1.
>  Perhaps it is now time to review that. Eg. one could use
> retrotranslator or retroweaver tools to run ASM on old JVMs.
>
>  regards,
>   Eugene
>
>
> On Tue, Jul 20, 2010 at 5:04 PM, Joshua Warner <[email protected]>
> wrote:
> > Hi,
> >
> > While reading through the documentation
> > (http://download.forge.objectweb.org/asm/asm-guide.pdf), I noticed a
> > discrepancy.  In that document, it seems to indicate that the ListS in
> > ClassNode are generic, e.g List<MethodNode> (see pages 83-84).  When
> looking
> > both the source code (SVN trunk) and the api documentation, I see that
> this
> > is not the case.
> >
> > Were these fields generic at the time the documentation was written?  If
> so,
> > why were they changed back?  If not, why not use generics?
> >
> > Regards,
> > Joshua
>
>
> --
> You receive this message as a subscriber of the [email protected] mailing list.
> To unsubscribe: mailto:[email protected]
> For general help: mailto:[email protected]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

-- 
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws