Jeroen Frijters wrote: > No, originally you wrote: > > The Sun API spec clearly states that > > Class.getClassLoader() may return > > null, and in fact MUST return null for primitive type > > Class objects. > > So why worry about obviously buggy software? > > I responded to this by saying that these vague spec statements don't > really help, in practice you have to be compatible with Sun's > implementation. Yes, it's legal to return null from getClassLoader > (IMHO, even for "application" classes), but in reality this breaks lots > of code. Yes, it's legal not to return null for "system" classes (e.g. > java.lang.Object), but again, I'm sure this will break some code.
OK, so we both agree that Sun's implementation sometimes returns null. What I'm curious about is: what are those cases that trigger the buggy software's bugs? Can you be more specific? I'm just trying to understand exactly what the issue is. What's a short program that behaves differently on two VMs? Etc. -Archie __________________________________________________________________________ Archie Cobbs * CTO, Awarix * http://www.awarix.com _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
