public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Andrey R. Urazov" <coola@localhost.localdomain> To: gcc-gnats@gcc.gnu.org Subject: c++/5529: ugly and unclear error message reporting that partial template specialization is not allowed for member function templates Date: Tue, 29 Jan 2002 05:36:00 -0000 [thread overview] Message-ID: <200201291303.TAA03139@localhost.localdomain> (raw) >Number: 5529 >Category: c++ >Synopsis: ugly and unclear error message reporting that partial template specialization is not allowed for member function templates >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Jan 29 05:36:03 PST 2002 >Closed-Date: >Last-Modified: >Originator: Andrey R. Urazov >Release: 3.0.3 >Organization: student of Novosibirsk State Technical University >Environment: System: Linux localhost 2.2.14-5.0 #19 Tue Jul 24 02:12:27 NOVST 2001 i586 unknown Architecture: i586 host: i586-pc-linux-gnu build: i586-pc-linux-gnu target: i586-pc-linux-gnu configured with: ../gcc-3.0.3/configure --enable-languages=c,c++ --disable-nls >Description: Instead of reporting that partial template specializatins are not allowed for member function templates, gcc outputs an unclear message: template_test.cpp:5: sorry, not implemented: `component_ref' not supported by dump_decl template_test.cpp:5: partial specialization `<declaration error><Q, Policy>' of function template >How-To-Repeat: struct Policy {}; struct B { template<class Q, class W> int getval(); template<class Q> int getval<Q, Policy>(); }; >Fix: fix dump_decl :) >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-01-29 13:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-29 5:36 Andrey R. Urazov [this message] 2002-05-19 5:01 lerdsuwa 2003-01-11 20:39 neroden
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=200201291303.TAA03139@localhost.localdomain \ --to=coola@localhost.localdomain \ --cc=coola@ngs.ru \ --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).