public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/50370] New: [C++0x] Multiple declarations with default template arguments accepted
Date: Mon, 12 Sep 2011 22:34:00 -0000	[thread overview]
Message-ID: <bug-50370-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 50370
           Summary: [C++0x] Multiple declarations with default template
                    arguments accepted
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: daniel.kruegler@googlemail.com
                CC: jason@redhat.com


gcc 4.7.0 20110903 (experimental) in C++0x mode accepts the following code:

template<class T, class = int>
void foo(T);

template<class T, class = int>
void foo(T) {}

template<class = int>
void bar();

template<class = int>
void bar() {}

int main() {
  foo(12);
  bar();
}

According to 14.1 [temp.param] p12 this code should be rejected:

"A template-parameter shall not be given default arguments by two different
declarations in the same scope. [ Example:
  template<class T = int> class X;
  template<class T = int> class X { /*... */ }; // error
—end example ]"

gcc correctly rejects such examples when class templates are involved, but
fails to do so for function templates. 

This looks very similar to bug 15339 or bug 48372, but the domain (default
template arguments) is different.


             reply	other threads:[~2011-09-12 21:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-12 22:34 daniel.kruegler at googlemail dot com [this message]
2012-01-28  6:28 ` [Bug c++/50370] " pinskia at gcc dot gnu.org
2013-09-16 14:34 ` jwillemsen at remedy dot nl
2020-07-16 17:07 ` mpolacek at gcc dot gnu.org
2020-07-16 17:29 ` mpolacek at gcc dot gnu.org
2022-03-09 13:50 ` ppalka 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-50370-4@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).