[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Japitools 1.5 support tough design issue
From: |
Stuart Ballard |
Subject: |
Re: Japitools 1.5 support tough design issue |
Date: |
Wed, 7 Sep 2005 09:59:29 -0400 |
On 9/7/05, Jeroen Frijters <address@hidden> wrote:
> Depends on what you mean by "Java" <g>. The JVM (outside of reflection
> support) has absolutely no knowledge of generics, so as far as the JIT
> and EE are concerned both are identical.
That was why I phrased my question as "any distinction at all" - I
know that different bits of the Java world have different levels of
understanding of generics :)
> > In other words, will there be any difference in bytecode between:
> > class MyList implements List
> > and
> > class MyList implements List<Object>
>
> The <Object> part is a separate attribute in the class file, but that
> attribute is only used for reflection and by Java compilers.
Hmm, sounds like Japitools should recognize that distinction, then.
Especially if it makes a difference to the compiler.
Out of interest, exactly what difference in behavior would you see in
the compiler and/or reflection based on those two different
declarations of MyList?
Stuart.
--
http://sab39.dev.netreach.com/
- Re: Japitools 1.5 support tough design issue, (continued)
RE: Japitools 1.5 support tough design issue, Jeroen Frijters, 2005/09/07
- Re: Japitools 1.5 support tough design issue,
Stuart Ballard <=
RE: Japitools 1.5 support tough design issue, Jeroen Frijters, 2005/09/07