From: Drew Adams <drew.adams@oracle.com>
To: rswgnu@gmail.com, emacs-devel <emacs-devel@gnu.org>
Subject: RE: Emacs 25.0.94: Is require failing to define macros and functions at compile time?
Date: Wed, 29 Jun 2016 08:16:10 -0700 (PDT) [thread overview]
Message-ID: <cfff40a5-1e28-44ce-a3b6-93b0503df24d@default> (raw)
In-Reply-To: <CA+OMD9gsA-HkRLURk0eusNeo5_Yg_znkrEN0YG1x0imHgGRWhA@mail.gmail.com>
> At the top of hact.el is:
> (mapc 'require '(hhist set))
I think that's your problem. The byte-compiler is probably
looking for a literal (require 'hhist) and (require 'set).
The Elisp manual, node `Named Features', says this:
When ‘require’ is used at top level in a file, it takes effect when
you byte-compile that file (*note Byte Compilation::) as well as when
you load it. This is in case the required package contains macros that
the byte compiler must know about. It also avoids byte compiler
warnings for functions and variables defined in the file loaded with
‘require’.
You might be able to get away with wrapping that `mapc' in an
`eval-when-compile'. But why bother with the `mapc' at all?
Just a guess - someone else will correct me if wrong.
next prev parent reply other threads:[~2016-06-29 15:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 14:55 Emacs 25.0.94: Is require failing to define macros and functions at compile time? Robert Weiner
2016-06-29 15:14 ` Clément Pit--Claudel
2016-06-29 15:44 ` Robert Weiner
2016-06-29 19:06 ` Davis Herring
2016-06-29 19:59 ` Drew Adams
2016-06-29 20:34 ` Robert Weiner
2016-06-29 20:59 ` Drew Adams
2016-06-29 21:04 ` John Mastro
2016-06-30 0:09 ` Herring, Davis
2016-06-30 5:56 ` Robert Weiner
2016-06-29 15:16 ` Drew Adams [this message]
2016-06-29 22:03 ` Michael Heerdegen
2016-06-29 22:09 ` Robert Weiner
2016-06-29 22:27 ` Michael Heerdegen
2016-06-29 22:42 ` Drew Adams
2016-06-29 23:14 ` Robert Weiner
2016-06-29 22:07 ` Michael Heerdegen
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=cfff40a5-1e28-44ce-a3b6-93b0503df24d@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=rswgnu@gmail.com \
/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).