public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de To: gcc-gnats@gcc.gnu.org Subject: c++/6644: g++ allows illegal access of private class members Date: Mon, 13 May 2002 05:26:00 -0000 [thread overview] Message-ID: <20020513121908.2773.qmail@sources.redhat.com> (raw) >Number: 6644 >Category: c++ >Synopsis: g++ allows illegal access of private class members >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: accepts-illegal >Submitter-Id: net >Arrival-Date: Mon May 13 05:26:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Volker Reichelt >Release: gcc 3.0.x, gcc 3.1 20020510 (prerelease) >Organization: >Environment: mips-sgi-irix6.5, i686-pc-linux-gnu >Description: The following code compiles fine, although "a.i" shouldn't be accessible in "B" ("i" is private in "A" and "B" is not a friend of "A"): -------------------------snip here------------------------ class A { int i; struct B { void foo () { A a; a.i; } }; }; -------------------------snip here------------------------ It's a regression from 2.95.x which correctly issues an error message. >How-To-Repeat: g++ -c Bug.cpp or even g++ -pedantic -c Bug.cpp >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-05-13 12:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-13 5:26 reichelt [this message] 2002-05-13 5:43 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=20020513121908.2773.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --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).