public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: chris@pennasoft.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/9061: Improper access granted to protected typedef from nested member of derived class Date: Mon, 06 Jan 2003 22:40:00 -0000 [thread overview] Message-ID: <20030106224044.13124.qmail@sources.redhat.com> (raw) Synopsis: Improper access granted to protected typedef from nested member of derived class State-Changed-From-To: open->closed State-Changed-By: bangerth State-Changed-When: Mon Jan 6 14:40:44 2003 State-Changed-Why: The standard was clarified and now states that member classes have all the same rights as member functions of a class. This rule applies here. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9061
next reply other threads:[~2003-01-06 22:40 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-06 22:40 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-26 12:46 chris
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=20030106224044.13124.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=chris@pennasoft.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --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: linkBe 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).