From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 24449@debbugs.gnu.org
Subject: bug#24449: Emacs 25.1 RC2: Byte compiler reports error in wrong place.
Date: Fri, 16 Sep 2016 16:22:08 +0300 [thread overview]
Message-ID: <83wpic3rpb.fsf@gnu.org> (raw)
In-Reply-To: <20160916113124.GB3630@acm.fritz.box> (message from Alan Mackenzie on Fri, 16 Sep 2016 11:31:25 +0000)
> Date: Fri, 16 Sep 2016 11:31:25 +0000
> From: Alan Mackenzie <acm@muc.de>
>
> $ emacs -Q -batch -f batch-byte-compile cc-engine.el
>
> . This outputs the following warning:
>
> In c-forward-decl-or-cast-1:
> cc-engine.el:8105:22:Warning: reference to free variable `eq'
>
> . The use of `eq' on L8105 is entirely correct. The error is at L8636,
> where the following appears:
>
> (and eq context nil
> (match-beginning 1))
>
> . Clearly parentheses around the `eq' form are missing.
>
> The compiler should have output its warning for L8636, not L8105.
Did you look at how the byte compiler determines the line number it
will include in the warning/error message? If you didn't, you should,
because after you do, you will never again wonder why an incorrect
line number is reported. In fact, now that I did look there, I'm
surprised it reports a correct line number at all, let alone as often
as it does. It's sheer luck.
next prev parent reply other threads:[~2016-09-16 13:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 11:31 bug#24449: Emacs 25.1 RC2: Byte compiler reports error in wrong place Alan Mackenzie
2016-09-16 13:22 ` Eli Zaretskii [this message]
2016-09-16 13:33 ` Alan Mackenzie
2016-09-16 15:09 ` Eli Zaretskii
2016-09-16 16:08 ` Alan Mackenzie
2016-09-16 18:34 ` Alan Mackenzie
2016-09-16 19:03 ` Eli Zaretskii
2016-09-17 8:29 ` Alan Mackenzie
2016-09-17 9:35 ` Eli Zaretskii
2016-09-17 10:06 ` Andreas Schwab
2016-09-17 12:58 ` Alan Mackenzie
2016-09-17 19:56 ` Michael Heerdegen
2016-09-17 20:46 ` Alan Mackenzie
2016-09-17 20:51 ` Michael Heerdegen
2016-09-17 20:59 ` Alan Mackenzie
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wpic3rpb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24449@debbugs.gnu.org \
--cc=acm@muc.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).