From: Florian Weimer <fw@deneb.enyo.de>
To: "Steven L. Zook" <SLZook@Qualstar.com>
Cc: "GCC Mailing List \(E-mail\)" <gcc@gcc.gnu.org>
Subject: Re: Nested Class Member Access
Date: Thu, 02 Sep 2004 19:22:00 -0000 [thread overview]
Message-ID: <87sma0v5ks.fsf@deneb.enyo.de> (raw)
In-Reply-To: <9E27B4AB55478346B9F7848926E49B7F4F7015@exchange1.qualstar.com> (Steven L. Zook's message of "Thu, 2 Sep 2004 12:13:13 -0700")
* Steven L. Zook:
> According to ISO/IEC 14882-2003 (is this the correct standard for
> GCC?) 11.8.1 [class.access.nest], I believe this should be an
> error. The paragraph says that nested classes have no special access
> rights to enclosing class members. Since cOuter::Variable is
> private, cOuter::cInner::Function should not have access to it.
Your are correct that your example is not valid C++, but this may
change:
<http://ra.dkuug.dk/jtc1/sc22/wg21/docs/cwg_defects.html#45>
next prev parent reply other threads:[~2004-09-02 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 19:13 Steven L. Zook
2004-09-02 19:22 ` Florian Weimer [this message]
2004-09-03 15:35 Steven L. Zook
2004-09-03 18:26 ` Giovanni Bajo
2004-09-03 21:15 ` Joe Buck
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=87sma0v5ks.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=SLZook@Qualstar.com \
--cc=gcc@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).