[asm] Re: Re: generics in ASM

[Rémi Forax <forax@xxxxxxxxxxx>]

Le 22/07/2010 00:52, Eugene Kuleshov a écrit :
> Ben Evans wrote:
> >  OK, I'll bite. Why would anyone care about pre-1.5 compatibility
> >  these days? Java 5 is EOL - it's dead, so why does it make sense to
> >  ship anything with support for older versions of Java than 5?
>
>  Because we can. :)

And SUN jdk5 is EOLed, not java 5 which is a spec.
IBM has several implementations of java 4 that aren't EOLed.

>  Anyways, the only packages that exposing non-generified collections 
> to the user API are asm.tree and asm.tree.analysis the rest is just 
> internally used collections.
>
>  Internally, in a few places, ASM breaks the rules of strongly-typed 
> collections and storing different objects within the same collection 
> and then using instanceof instead of virtual lookup. That stuff could 
> be rewritten to be strongly typed, but that will likely increase an 
> in-memory representation of the tree model. Anyways, performance 
> impact should be compared for any code changes.

We can also use Object as argument type (like in List<Object>) to avoid 
virtual lookup.

>  regards,
>  Eugene

cheers,
Rémi