public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: paolo@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8279: REGRESSION: failure to find a matching function in
Date: Mon, 21 Oct 2002 14:16:00 -0000 [thread overview]
Message-ID: <20021021211601.5812.qmail@sources.redhat.com> (raw)
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
next reply other threads:[~2002-10-21 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 14:16 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-21 12:46 Joe Buck
2002-10-21 9:36 Wolfgang Bangerth
2002-10-21 9:16 Joe Buck
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=20021021211601.5812.qmail@sources.redhat.com \
--to=bangerth@ticam.utexas.edu \
--cc=gcc-prs@gcc.gnu.org \
--cc=paolo@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).