public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/6372: private inheritance makes class totally inaccessible, even as parameter
Date: Fri, 19 Apr 2002 09:16:00 -0000	[thread overview]
Message-ID: <20020419161605.25293.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/6372; it has been noted by GNATS.

From: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com>
To: david@mandrakesoft.com
Cc: gcc-gnats@gcc.gnu.org, <nobody@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>,
        <gcc-bugs@gcc.gnu.org>, <gdr@codesourcery.com>
Subject: Re: c++/6372: private inheritance makes class totally inaccessible,
 even as parameter
Date: Fri, 19 Apr 2002 18:10:31 +0200 (CEST)

 Hi,
 
 > class A { };
 > class B : private A { };
 > class C : public B {
 > public:
 >     C(A*){}
 > };
 
 This looks inccorect according to 11.1 [#3] + DR #175.
 
 <--- part of DR 175 --->
 Proposed resolution (04/01):
 
 Add to the end of 11.1  class.access.spec paragraph 3:
 
 [Note: In a derived class, the lookup of a base class name will find the 
 injected-class-name instead of the name of the base class in the scope in 
 which it was declared. The injected-class-name might be less accessible 
 than the name of the base class in the scope in which it was declared.] 
 [Example:
 
 class A { };
     class B : private A { };
     class C : public B {
         A* p;    // error: injected-class-name A is inaccessible
         ::A* q;  // OK
     };
 
 --end example]
 
 What do you think Gaby?
 
 


             reply	other threads:[~2002-04-19 16:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-19  9:16 Gwenole Beauchesne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-15  5:16 nathan
2002-04-19  6:06 david

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=20020419161605.25293.qmail@sources.redhat.com \
    --to=gbeauchesne@mandrakesoft.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).