public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael.schlottke at sloede dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56328] Explicit instantiation of inline function template works for base template, fails for specialized template
Date: Fri, 15 Feb 2013 08:02:00 -0000	[thread overview]
Message-ID: <bug-56328-4-twDOWXyH3Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56328-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #4 from Michael Schlottke <michael.schlottke at sloede dot com> 2013-02-15 08:02:07 UTC ---
(In reply to comment #2)
> The foo<2> specialization is not declared in main.cpp before it would be
> needed, so the program is ill-formed, no diagnostic required, according to
> [templ.expl.spec]/6.

If I declare the foo<2> specialization in main.cpp, it does not change
anything.

> Also, the following paragraph is relevant:
> "When writing a specialization, be careful about its location, or to make it
> compile will be such a trial as to kindle its self-immolation."

I think this does not apply here (does it?), as it doesn't work even if I
declare foo<2> in both files after the base template.


  parent reply	other threads:[~2013-02-15  8:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 16:31 [Bug c++/56328] New: " michael.schlottke at sloede dot com
2013-02-14 18:45 ` [Bug c++/56328] " pinskia at gcc dot gnu.org
2013-02-14 20:40 ` redi at gcc dot gnu.org
2013-02-14 20:45 ` redi at gcc dot gnu.org
2013-02-15  8:02 ` michael.schlottke at sloede dot com [this message]
2013-02-15  8:06 ` michael.schlottke at sloede dot com
2013-02-15  9:11 ` redi at gcc dot gnu.org
2013-02-15  9:12 ` redi at gcc dot gnu.org
2013-02-15  9:24 ` michael.schlottke at sloede 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=bug-56328-4-twDOWXyH3Y@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).