public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/11987] [3.4/3.5 regression] Accepts-invalid with inherited nested type Date: Tue, 03 Feb 2004 14:06:00 -0000 [thread overview] Message-ID: <20040203140635.24870.qmail@sources.redhat.com> (raw) In-Reply-To: <20030819225102.11987.bangerth@dealii.org> ------- Additional Comments From giovannibajo at libero dot it 2004-02-03 14:06 ------- Wolfgang, I'm revisiting this bug. Y<dim>::I is a typedef for X<dim>::I. The standard does not explicitally forbids the use of typedef-names as qualifying scope in a constructor definition, and they are generally allowed for member functions. For instance, the following is trivially valid: struct C { C(); }; typedef C D; D::C() {} The only limitation I see is [comp.ctor]/3, which says that "a typedef-name that names a class shall not be used as the identifier in the declarator for a constructor declaration." but it is referring to the identifier itself, not to the qualified-id. Do you agree? I'm positive that your testcase is indeed valid. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |giovannibajo at libero dot | |it http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11987
next prev parent reply other threads:[~2004-02-03 14:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-08-19 22:51 [Bug c++/11987] New: ICE/accepts-invalid " bangerth at dealii dot org 2003-08-19 23:13 ` [Bug c++/11987] " pinskia at gcc dot gnu dot org 2003-08-23 1:23 ` [Bug c++/11987] [3.4 regression] " dhazeghi at yahoo dot com 2003-10-24 15:27 ` [Bug c++/11987] [3.4 regression] Accepts-invalid " lerdsuwa at gcc dot gnu dot org 2004-02-03 14:06 ` giovannibajo at libero dot it [this message] 2004-02-03 14:34 ` [Bug c++/11987] [3.4/3.5 " bangerth at dealii dot org 2004-02-28 2:31 ` mmitchel at gcc dot gnu dot org 2004-06-12 21:53 ` mmitchel at gcc dot gnu dot org 2005-04-21 4:58 ` [Bug c++/11987] [3.4/4.0/4.1 " mmitchel at gcc dot gnu dot org 2005-07-08 1:38 ` mmitchel at gcc dot gnu dot org 2005-09-27 20:58 ` mmitchel at gcc dot gnu dot 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=20040203140635.24870.qmail@sources.redhat.com \ --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).