public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bryce@gcc.gnu.org To: gcc-gnats@gcc.gnu.org Subject: java/4467: Ambiguous name resolution problem Date: Wed, 03 Oct 2001 23:46:00 -0000 [thread overview] Message-ID: <20011004064527.12895.qmail@sourceware.cygnus.com> (raw) >Number: 4467 >Category: java >Synopsis: Ambiguous name resolution problem >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: accepts-illegal >Submitter-Id: net >Arrival-Date: Wed Oct 03 23:46:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: bryce@gcc.gnu.org >Release: gcc version 3.1 20011003 (experimental) >Organization: >Environment: >Description: GCJ should reject this illegal code, because name resolution should stop at the innermost scope which defines "X". See JLS 6.5.2. package X; class Y {} class X { void a(X.Y xy) {} } >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-10-03 23:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-10-03 23:46 bryce [this message] 2003-05-12 19:15 Dara Hazeghi 2003-05-13 6:43 steven
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=20011004064527.12895.qmail@sourceware.cygnus.com \ --to=bryce@gcc.gnu.org \ --cc=gcc-gnats@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: linkBe 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).