public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xmh970252187 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/101356] New: The non-public member of a local class cannot be accessed by a friend of the class
Date: Wed, 07 Jul 2021 02:39:50 +0000 [thread overview]
Message-ID: <bug-101356-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101356
Bug ID: 101356
Summary: The non-public member of a local class cannot be
accessed by a friend of the class
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: xmh970252187 at gmail dot com
Target Milestone: ---
````
auto fun(){
void show();
struct C{
friend void show();
private:
int c;
};
return C{};
}
void show(){
auto o = fun();
o.c = 0;
}
````
Clang accepts this example while GCC rejects it by reporting an error
diagnosis.
As per [class.friend#1]
> A friend of a class is a function or class that is given permission to name the >private and protected members of the class. A class specifies its friends, if >any, by way of friend declarations. Such declarations give special access rights >to the friends, but they do not make the nominated friends members of the >befriending class.
next reply other threads:[~2021-07-07 2:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 2:39 xmh970252187 at gmail dot com [this message]
2021-08-02 15:35 ` [Bug c++/101356] " pinskia at gcc dot gnu.org
2021-12-13 15:58 ` pinskia at gcc dot gnu.org
2023-08-23 18:14 ` pinskia at gcc dot gnu.org
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=bug-101356-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).