Alan, Karen,
Can you review the fix for:
6612680: Remove classloader dependency on jkernel
Webrev at:
http://cr.openjdk.java.net/~mchung/6612680/
java.lang.ClassLoader and sun.misc.Launcher have explicit dependencies
on the jkernel code. While the performance impact of this is minimal
On Sat, 2009-10-03 at 23:43 -0500, Paul Benedict wrote:
I've always found it a bit perplexing that java.lang was never chosen
for the parent package of the Dynamic API. Why is that? Dynamic types
are now part of the language as proven by spec itself and exotic
identifiers. Will this be
Le 04/10/2009 08:03, Mandy Chung a écrit :
Alan, Karen,
Can you review the fix for:
6612680: Remove classloader dependency on jkernel
Webrev at:
http://cr.openjdk.java.net/~mchung/6612680/
java.lang.ClassLoader and sun.misc.Launcher have explicit dependencies
on the jkernel code. While
I thought the language was being modified to make Dynamic exempt
from type-checking rules. The way I look at it, grammar is the
underpinnings of language. To read the grammar is analogous to
compiling the source -- both are about making sense of tokens. With
the introduction of Dynamic, I have to
Stepan,
That is a very good observation. I wonder what others have to say
about it? As you pointed out, there are other java.lang.* sub-packages
that have no impact on the Java language.
I am in agreement that java.dyn is closer to the language than not --
hence I think java.lang.dyn is natural.
