public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: bagnara@cs.unipr.it, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/7809: befriending inaccessible names Date: Mon, 28 Oct 2002 14:55:00 -0000 [thread overview] Message-ID: <20021028225508.24427.qmail@sources.redhat.com> (raw) Old Synopsis: g++ 3.2 accepts friend declarations concerning inaccessible methods New Synopsis: befriending inaccessible names State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Mon Oct 28 14:55:07 2002 State-Changed-Why: As annoying as it seems, this is what the standard indeed says. There is a defect report (http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/cwg_closed.html#209) on the matter, which was put into "Not a defect" status, meaning gcc is indeed non-conforming. Confirmed with present CVS. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7809
reply other threads:[~2002-10-28 22:55 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021028225508.24427.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=bagnara@cs.unipr.it \ --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).