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: Package-private access checking in GCJ 3.3

From: Tom Tromey <tromey at redhat dot com>
To: Eric Blake <ebb9 at byu dot net>
Cc: Ranjit Mathew <rmathew at hotmail dot com>, java at gcc dot gnu dot org
Date: 19 Jun 2003 15:30:29 -0600
Subject: Re: Package-private access checking in GCJ 3.3
References: <3EECA38A.940157DC@hotmail.com> <87n0gjqhrl.fsf@fleche.redhat.com><bck2ig$8k2$1@main.gmane.org> <3EF1B13A.7010305@byu.net>
Reply-to: tromey at redhat dot com

>>>>> "Eric" == Eric Blake <ebb9@byu.net> writes:

>> *Except* for ACC_SUPER, everything else is there and has
>> the same value as defined by GCJ - what does ACC_SUPER mean?
>> Is it to specially flag references like "super.fooBar"?

Eric> Also read JVMS chapter 4 to see the history of these
Eric> values. ACC_SUPER is used for classes (it affects how super.m()
Eric> is resolved by the virtual machine). Note that a class is never
Eric> marked synchronized; ACC_SYNCHRONIZED is used for methods, which
Eric> are never marked super.

Incidentally, I don't think our interpreter properly handles this bit.
Ranjit, could you put this in bugzilla?  Or if someone has been
waiting to fix a relatively straightforward interpreter bug, have at
it.

Tom

Follow-Ups:
- Re: Package-private access checking in GCJ 3.3
  - From: Ranjit Mathew

References:
- Package-private access checking in GCJ 3.3
  - From: Ranjit Mathew
- Re: Package-private access checking in GCJ 3.3
  - From: Tom Tromey
- Re: Package-private access checking in GCJ 3.3
  - From: Ranjit Mathew
- Re: Package-private access checking in GCJ 3.3
  - From: Eric Blake

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