This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH, c++] tweak wording of `unknown type' in error messages
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Jason Merrill <jason at redhat dot com>
- Cc: Alexandre Oliva <aoliva at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: 01 Oct 2005 11:55:44 +0200
- Subject: Re: [PATCH, c++] tweak wording of `unknown type' in error messages
- References: <or8xxfr7sf.fsf@livre.oliva.athome.lsd.ic.unicamp.br><433E2232.8070701@redhat.com>
Jason Merrill <jason@redhat.com> writes:
| Alexandre Oliva wrote:
| > Unknown type is not something that necessarily makes sense to end
| > users, since it's just an internal representation detail of types yet
| > to undergo overload resolution. Some users seemed to be confused at
| > it, so I figured tweaking the wording a bit could make the problem
| > clearer.
|
| > * error.c (dump_type) <UNKNOWN_TYPE>: Print nondeduced or unknown.
|
| I think this change makes it even more confusing, since the type of
| the argument has nothing to do with template argument deduction. I
| suggested <overloaded function>, which is in fact where we get
| UNKNOWN_TYPEs.
I agree with Jason's suggestion.
-- Gaby