public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56323] [C++11] cannot compile inherited constructor for typedef'ed base class
Date: Thu, 14 Feb 2013 14:42:00 -0000 [thread overview]
Message-ID: <bug-56323-4-Jxjzx5UXCE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56323-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56323
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-02-14
CC| |jason at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2013-02-14 14:42:20 UTC ---
I think [class.qual]/2 says both C and D are valid.
C is valid because it is a using-declaration that is a member-declaration and
the name specified after the nested-name-specifier is the same as the
identifier in the last component of the nested-name-specifier.
D is valid because the name specified after the nested-name-specifier is the
injected-class-name of A.
In both cases the using-declaration names the constructor, so it declares a set
of inheriting constructors.
next prev parent reply other threads:[~2013-02-14 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 14:35 [Bug c++/56323] New: " t-gcc-bugzilla at snowelm dot com
2013-02-14 14:42 ` redi at gcc dot gnu.org [this message]
2013-02-14 16:42 ` [Bug c++/56323] " jason at gcc dot gnu.org
2013-02-15 1:27 ` jason at gcc dot gnu.org
2013-02-15 9:10 ` redi at gcc dot gnu.org
2013-02-15 11:17 ` paolo.carlini at oracle dot com
2013-02-27 18:14 ` 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-56323-4-Jxjzx5UXCE@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).