This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: confusion when CLASSPATH includes compiled class
- From: Andrew Haley <aph at redhat dot com>
- To: Per Bothner <per at bothner dot com>
- Cc: java at gcc dot gnu dot org
- Date: Tue, 22 Mar 2005 20:46:40 +0000
- Subject: Re: confusion when CLASSPATH includes compiled class
- References: <424081E2.7060707@bothner.com>
Per Bothner writes:
> Is this a known issue?
>
> If I run a gcj-compiled application that has class Foo.java/Foo.class
> compiled and linked into the executation, with a CLASSPATH that
> includes Foo.class then things get really confused.
> A Class.forName("Foo") will load the class in the CLASSPATH.
> On the other hand other native code will reference the native-class.
This is one of the things the new ABI will fix, for sure. However, I
thought Class.forName("Foo") should find the compiled class if it's in
the executable.
Andrew.