public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/4467: Ambiguous name resolution problem
Date: Mon, 12 May 2003 19:15:00 -0000 [thread overview]
Message-ID: <20030512190603.5581.qmail@sources.redhat.com> (raw)
The following reply was made to PR java/4467; it has been noted by GNATS.
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: bryce@gcc.gnu.org, gcc-gnats@gcc.gnu.org, tromey@gcc.gnu.org
Cc:
Subject: Re: java/4467: Ambiguous name resolution problem
Date: Mon, 12 May 2003 11:46:43 -0700
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
trail&database=gcc&pr=4467
Hello,
with gcc 3.2 the problem in this PR still appears. With 3.3 branch or
mainline (20030511) I get:
./X.java:3: error: Class `X.Y' already defined in X.java:3.
class Y {}
^
./X.java:5: error: Class `X.X' already defined in X.java:5.
class X
^
2 errors
Is this the correct error? Can this PR be closed? Thanks.
Dara
next reply other threads:[~2003-05-12 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 19:15 Dara Hazeghi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 6:43 steven
2001-10-03 23:46 bryce
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=20030512190603.5581.qmail@sources.redhat.com \
--to=dhazeghi@yahoo.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).