Re: Incorrect byte compiler error/warning message positions. A possible fix.

[Alan Mackenzie <acm@muc.de>]

Hello, Po.

On Mon, Nov 15, 2021 at 13:29:23 +0800, Po Lu wrote:
> Lars Ingebrigtsen <larsi@gnus.org> writes:

> >> The byte compiler reports wrong source positions in its error and
> >> warning messages; not every time, but perhaps most of the time.  There
> >> are currently at least six open bugs for this problem, e.g. bug #22288.

> > In my experience, the vast majority of the warning messages point to the
> > correct position.  But, yes, it does sometimes give the wrong position.

> I wouldn't say the "correct position", but somewhere close to the
> correct position.

> It could be, for example, a few lines above where it should actually be,
> when giving diagnostics for unused lexical bindings.

> But it is usually close enough for people to quickly locate and solve
> the error.

But not always.  As I said, there are at least six bug reports about
this problem.

My expectations are somewhat higher.  ;-)  How can we call ourselves
hackers, when we can't even produce a fully functional byte compiler?
I'm hoping to close this gap.

-- 
Alan Mackenzie (Nuremberg, Germany).