public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: hou_zhenyu@hotmail.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/9122: qualified name forced to be used in non-public derived class
Date: Thu, 02 Jan 2003 04:56:00 -0000	[thread overview]
Message-ID: <20030102045500.7523.qmail@sources.redhat.com> (raw)


>Number:         9122
>Category:       c++
>Synopsis:       qualified name forced to be used in non-public derived class
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jan 01 20:56:00 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     hou_zhenyu@hotmail.com
>Release:        unknown-1.0
>Organization:
>Environment:
Win2k + mingw2.0(gcc3.2, and rc2 of gcc3.2.1);
Redhad Linux 8.0 + gcc3.2
>Description:
If a class inhereit from another class which further non-publicly inherit yet another third class. Any member or parameters that use not full qualified name of the third class will fail to compile.

"`class XXX' is inaccessible"
in which XXX is the name of the third class.

gcc 2.95-3 does not has this problem.
>How-To-Repeat:
// test.cpp, compile with "g++ -c test.cpp"
class A {};

class B : A {};

class C : public B {
public:
	A* p; // compiler report : `class A' is inaccessible
};
>Fix:
// test.cpp
class A {};

class B : A {};

class C : public B {
public:
	::A* p; // full qualified, ok
};
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-01-02  4:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02  4:56 hou_zhenyu [this message]
2003-01-02  5:00 neil

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=20030102045500.7523.qmail@sources.redhat.com \
    --to=hou_zhenyu@hotmail.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).