From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 8712@debbugs.gnu.org
Subject: bug#8712: 24.0.50; getting the "Forgot to expand macro XXXX" error - problem? solution?
Date: Sun, 22 May 2011 13:00:24 -0700 [thread overview]
Message-ID: <385A7D1FFFBD41D4A0931558872D54E6@us.oracle.com> (raw)
In-Reply-To: <jwvr57qtzwg.fsf-monnier+emacs@gnu.org>
> I think the patch below fixes your problem, thanks. Please confirm.
I patched the corresponding functions by hand, loaded their original source
files, then loaded the patched functions. I then byte-compiled
icicles-cmd[12].el. No byte-compilation errors, so it seems, at least on the
surface, that this is fixed. The compilation was _very_ slow, but that's no
doubt because I used the source code rather than byte-compiled code.
Thanks for the fix.
I do have a question about the follownig warning, however (which I have not
seen/noticed before):
(lambda (opt) ...) quoted with ' rather than with #'
That presumably comes from a defmacro that has, in effect, this:
` ... (let* (... (something (lambda (opt)...))))
That is, an unquoted lambda inside a backquote. The backquote expands to (quote
(lambda...)) no doubt.
I have a few such macros, and I use them heavily. I get this same warning
zillions of times (460 times just for icicles-cmd1.el, 30 times for
icicles-cmd2.el). This is quite annoying.
What is the suggested/recommended way to write such code, to avoid this warning?
Do I now need to add #' in front of a lambda inside a backquote?
next prev parent reply other threads:[~2011-05-22 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 21:00 bug#8712: 24.0.50; getting the "Forgot to expand macro XXXX" error - problem? solution? Drew Adams
2011-05-21 21:06 ` Drew Adams
2011-05-22 18:14 ` Stefan Monnier
2011-05-22 20:00 ` Drew Adams [this message]
2011-05-23 1:36 ` Stefan Monnier
2011-05-23 3:55 ` Drew Adams
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=385A7D1FFFBD41D4A0931558872D54E6@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=8712@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).