public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/9050] [DR 147] Can't explicitly specialize C++ constructor templates
Date: Sat, 21 Nov 2009 06:34:00 -0000	[thread overview]
Message-ID: <20091121063413.15728.qmail@sourceware.org> (raw)
In-Reply-To: <bug-9050-2393@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from jason at gcc dot gnu dot org  2009-11-21 06:34 -------
Subject: Bug 9050

Author: jason
Date: Sat Nov 21 06:33:56 2009
New Revision: 154403

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=154403
Log:
        PR c++/9050, DR 147, DR 318
        * parser.c (cp_parser_lookup_name): If the name matches the explicit
        class scope, we're naming the constructor.
        (cp_parser_constructor_declarator_p): Just use cp_parser_unqualified_id
        if we have a nested-name-specifier.
        (cp_parser_direct_declarator): Handle getting an overload set as a
        constructor declarator.
        (cp_parser_unqualified_id): Avoid looking up the constructor when
        naming the destructor.
        (cp_parser_diagnose_invalid_type_name): Give good
        diagnostic for improper use of constructor as template.
        * typeck.c (finish_class_member_access_expr): Give good diagnostic
        about calling constructor.

        * error.c (dump_aggr_type): Don't print A::A for injected-class-name.

Added:
    trunk/gcc/testsuite/g++.dg/template/ctor9.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/error.c
    trunk/gcc/cp/parser.c
    trunk/gcc/cp/typeck.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/g++.dg/lookup/name-clash4.C
    trunk/gcc/testsuite/g++.dg/tc1/dr147.C
    trunk/gcc/testsuite/g++.old-deja/g++.jason/temporary5.C
    trunk/gcc/testsuite/g++.old-deja/g++.pt/ctor2.C


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9050


  parent reply	other threads:[~2009-11-21  6:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-9050-2393@http.gcc.gnu.org/bugzilla/>
2008-02-11 22:20 ` [Bug c++/9050] " vlad dot sharanhovich at gmail dot com
2008-02-11 23:44 ` manu at gcc dot gnu dot org
2008-10-26 22:02 ` manu at gcc dot gnu dot org
2009-11-20  5:17 ` jason at gcc dot gnu dot org
2009-11-21  3:19 ` [Bug c++/9050] [DR 147] " jason at gcc dot gnu dot org
2009-11-21  6:34 ` jason at gcc dot gnu dot org
2009-11-21  6:34 ` jason at gcc dot gnu dot org [this message]
     [not found] <bug-9050-4@http.gcc.gnu.org/bugzilla/>
2012-04-01 14:06 ` schaub.johannes at googlemail dot com
2012-04-01 14:15 ` schaub.johannes at googlemail dot com
2012-04-02  5:43 ` jason at gcc dot gnu.org
2012-04-02  7:45 ` schaub.johannes at googlemail dot com
2014-02-16 13:16 ` jackie.rosen at hushmail dot com

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=20091121063413.15728.qmail@sourceware.org \
    --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).