From: "Křištof Želechovski" <giecrilj@stegny.2a.pl>
To: gcc-help@gcc.gnu.org
Subject: mismatched paramters in error messages are reported as expressions and not types
Date: Wed, 21 Sep 2011 11:02:00 -0000 [thread overview]
Message-ID: <201109211308.20888.giecrilj@stegny.2a.pl> (raw)
g++ (4.6) recently threw at me the following error message:
doit.cpp:290:129: error: no match for ‘operator<<’ in ‘std::cout << boost::range::equal_range [with ForwardRange = boost::range_detail::transform_range<boost::value_factory<ls::file_rec<char>::as_char0>, std::vector<ls::file_rec<char> > >, Value = int, typename boost::range_iterator<const ForwardRange>::type = boost::transform_iterator<boost::value_factory<ls::file_rec<char>::as_char0>, __gnu_cxx::__normal_iterator<ls::file_rec<char>*, std::vector<ls::file_rec<char> > >, boost::use_default, boost::use_default>]((*(const boost::range_detail::transform_range<boost::value_factory<ls::file_rec<char>::as_char0>, std::vector<ls::file_rec<char> > >*)(& boost::range_detail::operator| [with InputRng = std::vector<ls::file_rec<char> >, UnaryFunction = boost::value_factory<ls::file_rec<char>::as_char0>]((* & lv_fr), (*(const boost::range_detail::transform_holder<boost::value_factory<ls::file_rec<char>::as_char0> >*)(& boost::adaptors::{anonymous}::transformed.boost::range_detail::forwarder<Holder>::operator() [with T = boost::value_factory<ls::file_rec<char>::as_char0>, Holder = boost::range_detail::transform_holder]((boost::value_factory<ls::file_rec<char>::as_char0>(), boost::value_factory<ls::file_rec<char>::as_char0>()))))))), (* &((int)a_n.std::basic_string<_CharT, _Traits, _Alloc>::operator[] [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>, std::basic_string<_CharT, _Traits, _Alloc>::reference = char&, std::basic_string<_CharT, _Traits, _Alloc>::size_type = long unsigned int](0ul))))’
Am I suppposed to read and understand this? It is overwhelming.
The same message, somewhat split, is a bit more readable:
doit.cpp:290:129:
error: no match for ‘operator<<’ in ‘
std::cout <<
boost::range::equal_range
[with
ForwardRange = boost::range_detail::transform_range<boost::value_factory<ls::file_rec<char>::as_char0>, std::vector<ls::file_rec<char> > >,
Value = int,
typename boost::range_iterator<const ForwardRange>::type =
boost::transform_iterator<
boost::value_factory<ls::file_rec<char>::as_char0>, __gnu_cxx::__normal_iterator<ls::file_rec<char>*, std::vector<ls::file_rec<char> > >, boost::use_default, boost::use_default>]
(
(
*
(const boost::range_detail::transform_range<boost::value_factory<ls::file_rec<char>::as_char0>, std::vector<ls::file_rec<char> > >*)
(
& boost::range_detail::operator| [with InputRng = std::vector<ls::file_rec<char> >, UnaryFunction = boost::value_factory<ls::file_rec<char>::as_char0>]
(
(* & lv_fr),
(
*
(const boost::range_detail::transform_holder<boost::value_factory<ls::file_rec<char>::as_char0> >*)
(
&
boost::adaptors::{anonymous}::transformed.boost::range_detail::forwarder<Holder>::operator()
[with T = boost::value_factory<ls::file_rec<char>::as_char0>, Holder = boost::range_detail::transform_holder]
((boost::value_factory<ls::file_rec<char>::as_char0>(), boost::value_factory<ls::file_rec<char>::as_char0>()))))))),
(
*
&
(
(int)
a_n.
std::basic_string<_CharT, _Traits, _Alloc>::operator[]
[with
_CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>,
std::basic_string<_CharT, _Traits, _Alloc>::reference = char&, std::basic_string<_CharT, _Traits, _Alloc>::size_type = long unsigned int](0ul))))’
What we can see is that the error message does not tell me the types that do not match but the expressions that do not match, and while subexpressions are sometimes marked with types, the type of the mismatched argument is only mentioned in the following notes. I mean, is it really necessary to dump the whole expression instead of just reporting the failing argument types? Is there a switch to turn it off?
Chris
next reply other threads:[~2011-09-21 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 11:02 Křištof Želechovski [this message]
2011-09-21 12:14 ` Jonathan Wakely
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=201109211308.20888.giecrilj@stegny.2a.pl \
--to=giecrilj@stegny.2a.pl \
--cc=gcc-help@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).