public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "harald at gigawatt dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/32039] Using declaration accepts non-visible members from base classes
Date: Sat, 10 Jan 2015 17:27:00 -0000 [thread overview]
Message-ID: <bug-32039-4-IXDrsteSBt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-32039-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32039
--- Comment #8 from Harald van Dijk <harald at gigawatt dot nl> ---
(In reply to Ville Voutilainen from comment #7)
> This is invalid. [namespace.udecl]/3 says that if the declaration names
> a constructor, the nested-name-specifier shall name a direct base, but if
> the declaration names something else than a constructor, indirect bases are
> fine.
Yes, but you're ignoring p14 (now p17 in N4140) which was mentioned right in
the initial report, which adds "The base class members mentioned by a
using-declaration shall be visible in the scope of at least one of the direct
base classes of the class where the using-declaration is specified." That is
not limited to constructors, that is a separate requirement in the standard
that GCC and clang both fail to implement.
next prev parent reply other threads:[~2015-01-10 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-32039-4@http.gcc.gnu.org/bugzilla/>
2011-11-22 8:51 ` fabien at gcc dot gnu.org
2014-02-28 21:41 ` fabien at gcc dot gnu.org
2014-02-28 21:43 ` fabien at gcc dot gnu.org
2014-02-28 21:53 ` fabien at gcc dot gnu.org
2014-03-01 0:03 ` harald at gigawatt dot nl
2014-03-01 7:53 ` fabien at gcc dot gnu.org
2015-01-10 16:46 ` ville.voutilainen at gmail dot com
2015-01-10 17:27 ` harald at gigawatt dot nl [this message]
2015-01-10 17:32 ` ville.voutilainen at gmail dot com
2015-01-10 18:12 ` ville.voutilainen at gmail dot com
2021-05-04 12:31 ` rguenth at gcc dot gnu.org
2007-05-22 12:07 [Bug c++/32039] New: " andrew dot stubbs at st dot com
2008-08-21 12:01 ` [Bug c++/32039] " gcc-bugzilla at contacts dot eelis dot net
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-32039-4-IXDrsteSBt@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).