public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9127: Misleading diagnostic for missing template<> introducing specialization
Date: Fri, 02 May 2003 18:36:00 -0000	[thread overview]
Message-ID: <20030502183600.5129.qmail@sources.redhat.com> (raw)

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
 


                 reply	other threads:[~2003-05-02 18:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030502183600.5129.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).