From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21963@debbugs.gnu.org
Subject: bug#21963: Spurious byte compile message: "Warning: the function `bar' might not be defined at runtime."
Date: Fri, 20 Nov 2015 11:40:50 +0000 [thread overview]
Message-ID: <20151120114050.GC10389@acm.fritz.box> (raw)
In-Reply-To: <83wptc6hqg.fsf@gnu.org>
Hello, Eli.
On Fri, Nov 20, 2015 at 01:19:19PM +0200, Eli Zaretskii wrote:
> > Date: Fri, 20 Nov 2015 10:44:19 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > This bug is a variant of bug #11918, which hasn't yet been resolved.
> I'm not sure this is the same issue.
Possibly not.
> > 1. Create two Emacs Lisp source files, ~/warnings-bar.el and
> > ~/warnings-foo.el with the following contents:
> > ;;;;;;;; warnings-bar.el ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> > (defun bar ()
> > "Doc string"
> > "bar")
> > (provide 'warning-bar)
> > ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> > ;;;;;;;; warnings-foo.el ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> > (eval-when-compile (require 'warning-bar))
> > (require 'warning-bar)
> > (defun foo ()
> > (bar))
> > ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> > 2. (Optional) byte compile warnings-bar.el.
> > 3. Byte compile warnings-foo.el with:
> > emacs -Q -batch -L ~ -f batch-byte-compile warning-foo.el
> > . This produces the spurious warning message:
> > warning-foo.el:6:1:Warning: the function `bar' might not be defined
> > at runtime.
> > .
> eval-when-compile has no effect at run time, and the warning is
> explicitly about what might happen at runtime.
> IOW, I don't think this is a bug.
It is, at the very least, puzzling behaviour. The warning is issued for
a function that most definitely has been defined at runtime.
What seems to be happening (I'm speculating a little) is that the byte
compiler maintains a list of not-yet-defined functions in
byte-compile-unresolved-functions. Functions defined at compile time
are pushed onto this list. The problem is that when they are later
defined for run time, they aren't taken off the list.
Given that we've all been asked to get rid of warnings for 25.1, I have
to disagree with you about whether this is a bug.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2015-11-20 11:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 10:44 bug#21963: Spurious byte compile message: "Warning: the function `bar' might not be defined at runtime." Alan Mackenzie
2015-11-20 11:19 ` Eli Zaretskii
2015-11-20 11:40 ` Alan Mackenzie [this message]
2015-11-20 14:48 ` Eli Zaretskii
2015-11-20 15:26 ` Alan Mackenzie
2015-11-20 15:48 ` Eli Zaretskii
2015-11-20 16:01 ` John Wiegley
2015-11-20 16:15 ` Alan Mackenzie
2015-11-20 16:44 ` John Wiegley
2015-11-20 17:50 ` Alan Mackenzie
2019-09-29 21:24 ` Stefan Kangas
2019-09-30 18:22 ` Alan Mackenzie
2019-09-30 21:24 ` Stefan Kangas
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=20151120114050.GC10389@acm.fritz.box \
--to=acm@muc.de \
--cc=21963@debbugs.gnu.org \
--cc=eliz@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.
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).