public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebor at roguewave dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/22263] explicit instantiation fails to emit symbols defined later
Date: Thu, 30 Jun 2005 23:57:00 -0000	[thread overview]
Message-ID: <20050630235659.14039.qmail@sourceware.org> (raw)
In-Reply-To: <20050630231800.22263.sebor@roguewave.com>


------- Additional Comments From sebor at roguewave dot com  2005-06-30 23:56 -------
I don't believe you are reading the paragraph correctly.

The paragraph applies to explicit instantiation. The reference to explicit
specialization allows members of the class template that is being explicitly
instantiated to be explicitly specialized prior to the explicit instantiation.

This allowance is necessary since the opposite (i.e., specializing the member
after the containing class template has been instantiated, explicitly or
otherwise) is not permitted.

-- 


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


  parent reply	other threads:[~2005-06-30 23:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 23:18 [Bug c++/22263] New: " sebor at roguewave dot com
2005-06-30 23:26 ` [Bug c++/22263] " pinskia at gcc dot gnu dot org
2005-06-30 23:36 ` sebor at roguewave dot com
2005-06-30 23:49 ` pinskia at gcc dot gnu dot org
2005-06-30 23:57 ` sebor at roguewave dot com [this message]
2005-07-01  0:06 ` sebor at roguewave dot com
2005-07-01 19:07 ` [Bug c++/22263] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-07-06 16:39 ` mmitchel at gcc dot gnu dot org
2005-07-17 23:10 ` mmitchel at gcc dot gnu dot org
2005-07-18 15:57 ` cvs-commit at gcc dot gnu dot org
2005-07-18 17:15 ` cvs-commit at gcc dot gnu dot org
2005-07-18 17:24 ` mmitchel at gcc dot gnu dot org
2005-10-01 17:07 ` pinskia 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=20050630235659.14039.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).