public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tromey@redhat.com
To: gcc-gnats@gcc.gnu.org
Subject: java/9547: member type access not respected
Date: Mon, 03 Feb 2003 18:06:00 -0000	[thread overview]
Message-ID: <20030203180211.1683.qmail@sources.redhat.com> (raw)


>Number:         9547
>Category:       java
>Synopsis:       member type access not respected
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 03 18:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Tom Tromey
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
Right now gcj will let a subclass see member type defined
in a superclass, even if that member type has default
access protection and the two classes are in different
packages.

For instance, this code compiles but should not.

package one;

import two.*;

public class o extends t
{
  boolean doit(Object x)
  {
    return x instanceof Res;
  }
}
package two;

public class t
{
  class Res
  {
  }
}


>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-02-03 18:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030203180211.1683.qmail@sources.redhat.com \
    --to=tromey@redhat.com \
    --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: 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).