This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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: PR java/19870 (Part 2/2): Handle private static methods accessed across nested classes

From: Tom Tromey <tromey at redhat dot com>
To: Ranjit Mathew <rmathew at gmail dot com>
Cc: GCJ Patches <java-patches at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: 19 Jun 2005 12:28:30 -0600
Subject: Re: PR java/19870 (Part 2/2): Handle private static methods accessed across nested classes
References: <39399b9d050618200363c78dbe@mail.gmail.com><m3ll57q6q1.fsf@localhost.localdomain><39399b9d05061911227bdffa3a@mail.gmail.com>
Reply-to: tromey at redhat dot com

>>>>> "Ranjit" == Ranjit Mathew <rmathew@gmail.com> writes:

>> If m() were not private, the call would be to Sub.m(), which would be
>> invalid because it would be a use of 'this' in a static context.

Ranjit> What static context?

In a super() or this() call the arguments are considered to be in a
static context.  The idea is that before the other constructor is
called, accesses via 'this' or 'super' are invalid.

Tom

References:
- PR java/19870 (Part 2/2): Handle private static methods accessed across nested classes
  - From: Ranjit Mathew
- Re: PR java/19870 (Part 2/2): Handle private static methods accessed across nested classes
  - From: Tom Tromey
- Re: PR java/19870 (Part 2/2): Handle private static methods accessed across nested classes
  - From: Ranjit Mathew

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