This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: null ClassLoader
- From: Tom Tromey <tromey at redhat dot com>
- To: Jeff Sturm <jsturm at one-point dot com>
- Cc: Torsten R|ger <torsten dot rueger at firsthop dot com>, java at gcc dot gnu dot org
- Date: 26 Nov 2001 11:02:58 -0700
- Subject: Re: null ClassLoader
- References: <Pine.LNX.4.10.10110261438080.10354-100000@mars.deadcafe.org>
- Reply-to: tromey at redhat dot com
>>>>> "Jeff" == Jeff Sturm <jsturm@one-point.com> writes:
[ some old email ]
Torsten> Yes, but it hasn't been implemented. Why ? Such a small
Torsten> thing.
Jeff> Maybe because the correct semantics aren't that obvious? Sun
Jeff> has both a bootclasspath & classpath; gcj does not. There is no
Jeff> simple way to distinguish classes that are linked into the final
Jeff> executable (whether static or not) from libgcj classes.
Couldn't we just return the same class loader for bootstrap classes as
well as user-defined classes? I don't think any of our code relies on
the class loader being null. So we might as well make this change,
just to make things convenient for those who assume that class loaders
are never null. Is there any reason not to make the change?
Tom