This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: native vs class Classes
- From: Tom Tromey <tromey at redhat dot com>
- To: Stéphane Konstantaropoulos <stephane at cs dot york dot ac dot uk>
- Cc: java at gcc dot gnu dot org
- Date: 30 Nov 2004 16:03:03 -0700
- Subject: Re: native vs class Classes
- References: <1101407871.6679.8.camel@pc153>
- Reply-to: tromey at redhat dot com
>>>>> "Stéphane" == Stéphane Konstantaropoulos <stephane@cs.york.ac.uk> writes:
Stéphane> When you load a class from a natively compiled java program by doing:
Stéphane> Class.forName("com.mysql.jdbc.Driver");
Stéphane> It loads the .class file -- from the classpath.
Stéphane> How about all the classes that are referenced in that class? does it
Stéphane> need to load them too? Or can it look them up in the
Stéphane> natively compiled library (I mean mostly the standard
Stéphane> classes that are in libgcj.so)?
Historically the way it has worked is that interpreted classes can
refer to compiled classes, but not vice versa. The new binary
compatibility ABI (just merged in, will appear in GCC 4.0) lets you
freely intermix interpreted and compiled code.
Stéphane> Does someone have some documentation on how class loading works in
Stéphane> libgcj somewhere?
There is some information in the gcj manual, but probably not enough.
This is a good time to fix the manual, if you've got suggestions...
Tom