Tim Ellison wrote:
Matt> Wasn't one of the issues here the theoretical "What
Matt> happens when Sun defines a public VMClass class in
Matt> java.lang?"
There's no bad (i.e., security violating) situation that can arise
from this. It is no different from Sun adding any other class that is
not yet implemented in Classpath.
There would be a namespace collision though (I'd guess the risk is small
tho')
Not an issue: code that relies on Sun's new class wouldn't compile
or run properly with the yet-to-be updated Classpath in either case!
-Archie
__________________________________________________________________________
Archie Cobbs * CTO, Awarix * http://www.awarix.com
