From: John Wiegley <jwiegley@gmail.com>
To: Alan Mackenzie <acm@muc.de>
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 08:44:56 -0800 [thread overview]
Message-ID: <m2vb8wzkl3.fsf@newartisans.com> (raw)
In-Reply-To: <20151120161535.GE10389@acm.fritz.box> (Alan Mackenzie's message of "Fri, 20 Nov 2015 16:15:35 +0000")
>>>>> Alan Mackenzie <acm@muc.de> writes:
> While eval-when-compile'ing the first line, the byte compiler collects a
> list of symbols defined by it (in variable
> byte-compile-noruntime-functions). More or less.
> There is no mechanism for taking symbols off of that list when they
> subsequently become defined.
Not optimal, but I must ask: Should it be fixed? Or, for now, simply noted in
the elisp manual when discussing the merits of this warning?
John
next prev parent reply other threads:[~2015-11-20 16:44 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
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 [this message]
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=m2vb8wzkl3.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=21963@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).