Re: java/4467: Ambiguous name resolution problem

Re: java/4467: Ambiguous name resolution problem

[steven]

Synopsis: Ambiguous name resolution problem

State-Changed-From-To: open->feedback
State-Changed-By: steven
State-Changed-When: Tue May 13 06:43:45 2003
State-Changed-Why:
    Looks fixed -- please confirm.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4467

Re: java/4467: Ambiguous name resolution problem

[Dara Hazeghi]

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
 

java/4467: Ambiguous name resolution problem

[bryce]

>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: