public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: veksler@il.ibm.com To: gcc-gnats@gcc.gnu.org Subject: c++/3538: g++ should not allow friend to inaccessible members. Date: Tue, 03 Jul 2001 02:36:00 -0000 [thread overview] Message-ID: <20010703092830.22954.qmail@sourceware.cygnus.com> (raw) >Number: 3538 >Category: c++ >Synopsis: g++ should not allow friend to inaccessible members. >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: accepts-illegal >Submitter-Id: net >Arrival-Date: Tue Jul 03 02:36:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: veksler@il.ibm.com >Release: gcc-3.0 >Organization: >Environment: powerpc-ibm-aix4.3.3.0 >Description: G++ does not enforce the following rule: "A name nominated by a friend declaration shall be accessible in the scope of the class containing the friend declaration" This is a quote from 11.4.7 of the 2 December 1996 draft. IMHO this is a bad rule that gcc may chose not to implement, but it should at least be optional. Some compilers do enforce this rule. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="friend.cc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="friend.cc" Y2xhc3MgQSB7CiAgcHVibGljOiAgICAKICAgICB2b2lkIHB1YmxpY19mdW5jKCk7CiAgcHJpdmF0 ZToKICAgICB2b2lkIHByaXZhdGVfZnVuYygpOwp9OwoKY2xhc3MgQiB7CiAgLy8gVGhpcyBpcyBp bGxlZ2FsLCBiZWNhdXNlICdwcml2YXRlX2Z1bmMnIGlzIGluYWNjZXNzaWJsZSBhdCB0aGlzIHBv aW50LgogIGZyaWVuZCB2b2lkIEE6OnByaXZhdGVfZnVuYygpOwp9Owo=
next reply other threads:[~2001-07-03 2:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-03 2:36 veksler [this message] 2001-07-08 9:21 nathan
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=20010703092830.22954.qmail@sourceware.cygnus.com \ --to=veksler@il.ibm.com \ --cc=gcc-gnats@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).