public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/9127: Misleading diagnostic for missing template<> introducing specialization
@ 2003-05-02 18:36 Giovanni Bajo
0 siblings, 0 replies; only message in thread
From: Giovanni Bajo @ 2003-05-02 18:36 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR c++/9127; it has been noted by GNATS.
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: <gcc-gnats@gcc.gnu.org>,
<gcc-bugs@gcc.gnu.org>,
<nobody@gcc.gnu.org>,
<gcc-prs@gcc.gnu.org>,
<schmid@snake.iap.physik.tu-darmstadt.de>
Cc:
Subject: Re: c++/9127: Misleading diagnostic for missing template<> introducing specialization
Date: Fri, 2 May 2003 20:29:05 +0200
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9127
Well, the problem is that the compiler is entering an instantiation
recursion which should be terminated by the explicit specialization. Since
the spiecialization is invalid (and skipped by the compiler), the loop never
ends.
The problem about the too long output is already covered by c++/9335. So, I
keep this PR open only because the diagnostic of 3.4 could be improved:
-----------------------------------
template <int>
struct A;
struct A<0>
{};
-----------------------------------
pr9127.cpp:5: error: too few template-parameter-lists
The same code snippet on Comeau gives:
"pr9127.cpp", line 4: error: specializing class "A<0>" without "template<>"
syntax is nonstandard
which is _far_ better.
Giovanni Bajo
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-05-02 18:36 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-02 18:36 c++/9127: Misleading diagnostic for missing template<> introducing specialization Giovanni Bajo
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).