This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/8279: REGRESSION: failure to find a matching function in
- From: Wolfgang Bangerth <bangerth at ticam dot utexas dot edu>
- To: paolo at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 21 Oct 2002 21:16:01 -0000
- Subject: Re: c++/8279: REGRESSION: failure to find a matching function in
- Reply-to: Wolfgang Bangerth <bangerth at ticam dot utexas dot edu>
The following reply was made to PR c++/8279; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: jbuck@synopsys.com, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>,
<paolo@gcc.gnu.org>
Cc:
Subject: Re: c++/8279: REGRESSION: failure to find a matching function in
Date: Mon, 21 Oct 2002 16:09:39 -0500 (CDT)
> Even if gcc's behavior is correct, the diagnostic is puzzling:
>
> PREFIX/include/c++/3.2.1/bits/stream_iterator.h:141: no
> match for `std::basic_ostream<char, std::char_traits<char> >& << const
> std::pair<std::string, unsigned int>&' operator
>
> when there is what appears to be an exact match. Strategies to come up
> with a better diagnostic (e.g. tell the user why the function s/he
> intended to use isn't accepted) would be wlcome.
Maybe a first simple step would be to change the message to say
no match for `...' found during name lookup
Indicating that there _might_ even be such a name, but that it just was
not found. This would at least give a clue as to what may be going wrong.
Regards
Wolfgang
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ticam.utexas.edu
www: http://www.ticam.utexas.edu/~bangerth