This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: confusion when CLASSPATH includes compiled class

From: Per Bothner <per at bothner dot com>
To: tromey at redhat dot com
Cc: java at gcc dot gnu dot org
Date: Wed, 23 Mar 2005 12:15:41 -0800
Subject: Re: confusion when CLASSPATH includes compiled class
References: <424081E2.7060707@bothner.com> <42408386.2080407@bothner.com> <424094CF.2050302@bothner.com> <m3u0n22kug.fsf@localhost.localdomain>

Tom Tromey wrote:

"Per" == Per Bothner <per@bothner.com> writes:
Per> I think I understand what is going on, at least for interpreted classes.
[...]
Per> Does this analysis seem correct?
Yes. Thanks for looking at this.

A related issue:

From my reading of Sun's JavaDoc for java.lang.reflect.Field, I conclude
that the getXxx methods need to initialize the declaring class, if it
hasn't been.  I don't see any code to do this.

Likewise for setXxx, and invoke on a Method instance.
--
	--Per Bothner
per@bothner.com   http://per.bothner.com/

Follow-Ups:
- Re: confusion when CLASSPATH includes compiled class
  - From: Tom Tromey

References:
- confusion when CLASSPATH includes compiled class
  - From: Per Bothner
- Re: confusion when CLASSPATH includes compiled class
  - From: Per Bothner
- Re: confusion when CLASSPATH includes compiled class
  - From: Per Bothner
- Re: confusion when CLASSPATH includes compiled class
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]