Re: Re: Generics in ASM APIs?

What is the criteria for abandoning JDK 1.3/1.4 support so that
annotations can be fully embraced?  Or is there a desire to avoid some
kind of overhead associated with generics, rather than just purely
support for older JDKs?

On Wed, Jan 5, 2011 at 7:30 AM, Rémi Forax <[email protected]> wrote:
> On 01/01/2011 12:21 AM, [email protected] wrote:
>>
>> I've been searching the archive for this, haven't found much.
>>
>> Is there any plan to apply generics to collections in the ASM APIs?  I use
>> the
>> Tree API and I'd prefer ClassNode to define List<AnnotationNode>  (and so
>> forth)
>> rather than just List.
>>
>> I realize that ASM predates JDK 1.5 generics, but that's five years ago
>> now!
>
> There is a plan in my mind :)
>
> The idea is to generify ASM but customize the optimizer to generate 1.3
> compatible bytecode.
> With that, asm-all.jar will be 1.3 compatible but asm-all-debug.jar will be
> 1.5.
> So you can compile using asm-all-debug.jar and use generics and
> run using asm-all.jar which is as small as always.
>
> Alas, I have no time to play with that idea,
> but I can sponsor anyone who want to try :)
>
> Rémi
>
>
>
>
> --
> 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
>
>



-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

-- 
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