public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: oliver@mpi-sb.mpg.de To: gcc-gnats@gcc.gnu.org Subject: c++/3300: using declaration does not change member accessibility correctly Date: Wed, 20 Jun 2001 11:46:00 -0000 [thread overview] Message-ID: <20010620184330.29248.qmail@sourceware.cygnus.com> (raw) >Number: 3300 >Category: c++ >Synopsis: using declaration does not change member accessibility correctly >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Jun 20 11:46:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: g++ >Release: 3.0 >Organization: >Environment: Suse Linux 7.1/ kernel 2.2.18 >Description: The using-declaration in the example below does not change the accessibility of the foo-members as expected. According to the ISO-C++ standard (section 7.3.3/14), "all instances of the name mentioned in a using-declaration shall be accessible". In the example, g++ grants access only to the const version of foo, not to the mutable variant and thus complains with test.C:19: assignment of read-only location. Another funny thing: changing the declaration order of the two foo versions in the base class makes the mutable version available and lets g++ compile the code. g++ 2.95.3 did not have that kind of trouble. >How-To-Repeat: class A { public: int& foo() { return x; } const int& foo() const { return x; } int x; }; class B : private A { public: using A::foo; }; int main() { B b; b.foo() = 5; } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-06-20 11:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-20 11:46 oliver [this message] 2001-08-11 13:38 gdr
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=20010620184330.29248.qmail@sourceware.cygnus.com \ --to=oliver@mpi-sb.mpg.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).