public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rguenth@tat.physik.uni-tuebingen.de To: gcc-gnats@gcc.gnu.org Subject: c++/7075: Specialization of template in template does not work Date: Wed, 19 Jun 2002 05:46:00 -0000 [thread overview] Message-ID: <20020619111731.21692.qmail@sources.redhat.com> (raw) >Number: 7075 >Category: c++ >Synopsis: Specialization of template in template does not work >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Wed Jun 19 04:26:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Richard Guenther >Release: gcc 3.1.1 CVS >Organization: >Environment: Linux bellatrix 2.4.18-rc4-TATUP #2 Tue Mar 19 16:30:05 CET 2002 i686 unknown >Description: The attached code fails to compile using any version of g++ which complains part-broken.cpp:10: template parameters not used in partial specialization: part-broken.cpp:10: `T' part-broken.cpp: In static member function `static void foo<T>::bar<d>::blah(T) [with int d = -46, T = int]': and then fails to use/recognize the specialization, i.e. exceeds maximum template instantiation depth. >How-To-Repeat: g++ -c -Wall part-broken.cpp >Fix: One can work around this by adding an extra template parameter to the inner class defaulting to the template class of the outer class. See .cpp file. >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/plain; name="part-broken.cpp" Content-Disposition: inline; filename="part-broken.cpp" template <typename T> struct foo { /* works, if template <int d, typename X = T> and use X for T */ template <int d> struct bar { static void blah(T x) { bar<d-1>::blah(x); } }; struct bar<0> { static void blah(T x) { } }; }; int main(int argc, char **argv) { foo<int>::bar<3>::blah(5); return 0; }
next reply other threads:[~2002-06-19 11:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-19 5:46 rguenth [this message] 2002-06-24 7:37 lerdsuwa
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=20020619111731.21692.qmail@sources.redhat.com \ --to=rguenth@tat.physik.uni-tuebingen.de \ --cc=gcc-gnats@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: linkBe 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).