public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55655] cannot export specialized template
Date: Tue, 11 Dec 2012 20:49:00 -0000	[thread overview]
Message-ID: <bug-55655-4-c9AIsf8Xye@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55655-4@http.gcc.gnu.org/bugzilla/>


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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2012-12-11
     Ever Confirmed|0                           |1

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-12-11 20:48:56 UTC ---
(In reply to comment #0)
> Let us say I have a generic template class, e.g. my_smart_ptr. Let us also say
> I have a class 'foo', 'clas foo : public my_smart_ptr<bar>' that is part of
> some library public API. And last, let us say that 'foo' needs to specialize
> 'my_smart_ptr<bar>'.

Please provide some code instead of saying it.  It's much easier to talk about
concrete examples, with the compiler commands used.


  reply	other threads:[~2012-12-11 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 20:15 [Bug c++/55655] New: " mw_triad at users dot sourceforge.net
2012-12-11 20:49 ` redi at gcc dot gnu.org [this message]
2012-12-11 21:06 ` [Bug c++/55655] " mw_triad at users dot sourceforge.net
2012-12-11 21:49 ` redi at gcc dot gnu.org
2012-12-11 23:34 ` mw_triad at users dot sourceforge.net

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-55655-4-c9AIsf8Xye@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).