This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/53152] In "no match for operatorXX" error message gives the wrong column info
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 04 May 2012 11:27:15 +0000
- Subject: [Bug c++/53152] In "no match for operatorXX" error message gives the wrong column info
- Auto-submitted: auto-generated
- References: <bug-53152-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53152
Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|lopezibanez at gmail dot |manu at gcc dot gnu.org
|com |
--- Comment #4 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> 2012-05-04 11:27:15 UTC ---
(In reply to comment #3)
> How could we in principle fix this? Pass down from cp_parser_binary_expression
> the location of the operator token, through build_x_binary_op -> build_new_op
> -> build_new_op_1 -> op_error? Boring but straightforward. Or something else
> entirely? I'm just guessing, really.
Since we don't pass down the expression itself, I don't see any other way than
passing down the location. In general almost all build_* function should be
build_*(location_t loc,...). Thanks for doing this, it will improve the caret a
lot (and perhaps the debugging experience).