From: Joe Buck <Joe.Buck@synopsys.COM>
To: Giovanni Bajo <rasky@develer.com>
Cc: "Steven L. Zook" <SLZook@Qualstar.com>, gcc@gcc.gnu.org
Subject: Re: Nested Class Member Access
Date: Fri, 03 Sep 2004 21:15:00 -0000 [thread overview]
Message-ID: <20040903141514.B343@synopsys.com> (raw)
In-Reply-To: <0ca201c491e3$85d8acf0$f503030a@mimas>; from rasky@develer.com on Fri, Sep 03, 2004 at 08:26:26PM +0200
On Fri, Sep 03, 2004 at 08:26:26PM +0200, Giovanni Bajo wrote:
> Steven L. Zook wrote:
>
> > Is this behavior on GCC's part (that is, nested classes are members of the
> > enclosing class and thus have all access rights that other members have)
> > intentional?
>
> Yes.
>
> > If so, should it be documented in the "Extensions to the C++ Language"
> > section of the GCC online documents.
>
> Not really, because it is actually part of C++0x, so it is not a real
> extension in the traditional term. Instead, I would like to define a new
> language dialect (-std=c++0x) to activate such behavours (that is,
> implementation of DRs which are in WP status). There have been some talk
> about it, but no patches yet.
Speaking of c++0x, I'd dearly like to see an implementation of the "auto"
proposal that Stroustrup has championed, so loops iterating over
containers can be written simply and uniformly as
for (auto iter = container.begin(); iter != container.end(); ++iter) {
...;
}
next prev parent reply other threads:[~2004-09-03 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 15:35 Steven L. Zook
2004-09-03 18:26 ` Giovanni Bajo
2004-09-03 21:15 ` Joe Buck [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-02 19:13 Steven L. Zook
2004-09-02 19:22 ` Florian Weimer
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=20040903141514.B343@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=SLZook@Qualstar.com \
--cc=gcc@gcc.gnu.org \
--cc=rasky@develer.com \
/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).