public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, lalle@sics.se, nobody@gcc.gnu.org Subject: Re: c++/10147: [3.2/3.3/3.4 regression] Confusing error message for invalid template function argument Date: Thu, 20 Mar 2003 02:09:00 -0000 [thread overview] Message-ID: <20030320020919.12202.qmail@sources.redhat.com> (raw) Old Synopsis: Confusing error message for invalid template function argument New Synopsis: [3.2/3.3/3.4 regression] Confusing error message for invalid template function argument State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Thu Mar 20 02:09:19 2003 State-Changed-Why: Confirmed. I think this is a regression: 2.95 said on this code x.cc: In function `void N2::f(const N1::B &)': x.cc:32: conversion from `A' to non-scalar type `N2::A' requested x.cc:26: in passing argument 1 of `N2::tf<N2::A>(const N2::A &)' This is not entirely accurate, since A is actually N1::A, but the message was much clearer than what we get presently (in 3.2, 3.3 and mainline). W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10147
reply other threads:[~2003-03-20 2:09 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=20030320020919.12202.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=lalle@sics.se \ --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: 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).