public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jens.maurer at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/55972] New: cannot access private member from lambda used in NSDMI Date: Mon, 14 Jan 2013 16:14:00 -0000 [thread overview] Message-ID: <bug-55972-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55972 Bug #: 55972 Summary: cannot access private member from lambda used in NSDMI Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: jens.maurer@gmx.net The following short translation unit shows the issue: class C { void f(); int j = 10; int i = [this]() { return this->j; }(); }; $ g++ -std=c++11 x.cc x.cc: In lambda function: x.cc:4:11: error: ‘int C::j’ is private x.cc:5:39: error: within this context Non-static data member initializers (and lambdas used therein) should be able to access private members of their class.
next reply other threads:[~2013-01-14 16:14 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-14 16:14 jens.maurer at gmx dot net [this message] 2013-01-14 16:43 ` [Bug c++/55972] " redi at gcc dot gnu.org 2013-03-12 21:41 ` jason at gcc dot gnu.org 2013-03-17 2:40 ` jason at gcc dot gnu.org 2013-03-23 19:20 ` jason 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-55972-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: 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).