From: Alan Mackenzie <acm@muc.de>
To: 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 10:44:19 +0000 [thread overview]
Message-ID: <20151120104419.GA10389@acm.fritz.box> (raw)
Hello Emacs.
Using the latest from the emacs-25 branch:
This bug is a variant of bug #11918, which hasn't yet been resolved.
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.
.
N.B. if the `eval-when-compile' form is removed from warnings-foo.el, the
warning is not produced.
--
Alan Mackenzie (Nuremberg, Germany).
next reply other threads:[~2015-11-20 10:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 10:44 Alan Mackenzie [this message]
2015-11-20 11:19 ` bug#21963: Spurious byte compile message: "Warning: the function `bar' might not be defined at runtime." Eli Zaretskii
2015-11-20 11:40 ` Alan Mackenzie
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=20151120104419.GA10389@acm.fritz.box \
--to=acm@muc.de \
--cc=21963@debbugs.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).