public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/8899: gcj confused over local classes
Date: Fri, 13 Dec 2002 09:26:00 -0000 [thread overview]
Message-ID: <20021213172601.21054.qmail@sources.redhat.com> (raw)
The following reply was made to PR java/8899; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: gbenson@redhat.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/8899: gcj confused over local classes
Date: 13 Dec 2002 10:20:25 -0700
>>>>> "Gary" == Gary Benson <gbenson@redhat.com> writes:
Gary> Number: 8899
Gary> Synopsis: gcj confused over local classes
Gary> | public class Test {
Gary> | public void func1() {
Gary> | class Foo {
Gary> | Foo(int i) {
Gary> | }
Gary> | }
Gary> | Foo f = new Foo(1);
Gary> | }
Gary> | public void func2() {
Gary> | class Foo {
Gary> | Foo(boolean b) {
Gary> | }
Gary> | }
Gary> | }
Gary> | }
I looked at this last night.
It turns out that gcj has no notion of scope for member classes. It
puts them all in a single list attached to the class. So the problem
is that basic required functionality is missing from gcj.
Tom
next reply other threads:[~2002-12-13 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 9:26 Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-11 2:16 gbenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021213172601.21054.qmail@sources.redhat.com \
--to=tromey@redhat.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).