From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: eval-when-compile and require
Date: Thu, 23 Nov 2017 06:22:58 +0100 [thread overview]
Message-ID: <86fu95tvpp.fsf@zoho.com> (raw)
In-Reply-To: mailman.4288.1511318543.27995.help-gnu-emacs@gnu.org
Stefan Monnier wrote:
>> (eval-when-compile (require 'foo))
>> [...] (info "(elisp) Warning Tips")
>
> I suggest you M-x report-emacs-bug, since
> that doc is incorrect (you'll still get
> warnings along the lines of "those functions
> are not known to be defined at runtime").
Close!
Actually it says "might not be defined at
runtime" :)
And it only mentions `cl-find-if' - not
`cl-caddr' or `cl-case' (?). Perhaps they have
some different status or location within the
CL library?
Also, looking at the fallout below, is it
likely that `eval-and-compile' (N.B. -and-, not
-when-) is what they meant in
(info "(elisp) Warning Tips") ?
Here is the compilation function:
#! /bin/zsh
compile-one () {
local file=$1
emacs -Q -batch -f batch-byte-compile $file
}
Using functions form `cl-lib', and not doing
anything about it:
In end of data:
wrap-search-cp.el:133:1:Warning: the
following functions are not known to be
defined: cl-find-if, cl-caddr, cl-case
using (require 'cl-lib)
no errors or warnings
using (eval-when-compile (require 'cl-lib))
In end of data:
wrap-search-cp.el:133:1:Warning: the
function `cl-find-if' might not be defined
at runtime.
using (eval-and-compile (require 'cl-lib))
no errors or warnings
--
underground experts united
http://user.it.uu.se/~embe8573
prev parent reply other threads:[~2017-11-23 5:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 4:05 eval-when-compile and require Emanuel Berg
2017-11-21 7:29 ` tomas
2017-11-21 16:55 ` Emanuel Berg
2017-11-22 2:42 ` Stefan Monnier
2017-11-22 14:03 ` Emanuel Berg
2017-11-23 5:25 ` Emanuel Berg
2017-11-27 2:51 ` Emanuel Berg
[not found] ` <mailman.4288.1511318543.27995.help-gnu-emacs@gnu.org>
2017-11-23 5:22 ` Emanuel Berg [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86fu95tvpp.fsf@zoho.com \
--to=moasen@zoho.com \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.