https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118793
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot
gnu.org
--- Comment #3 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to urbanjost from comment #2)
> I can imagine that different parsing of the input might make this very
> difficult but might also be very straight-forward so was hoping for the
> best. With small inputs it is not too bad, but errors in input can be
> particularly difficult to find with no location provided when large input
> files are involved so even if the location is not available printing
> adjacent characters would be a significant improvement by itself.
I did actually start looking at this last week. I do see where I can get at
additional information and I was thinking at the time something along the lines
of "at or near the the text 'some text'.
In the parsing there is a lot get the next character and un-get it if its not
this or that. It is complicated.
