From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 11847@debbugs.gnu.org
Subject: bug#11847: 24.1.50; Error: Don't know how to compile #[nil "..."]
Date: Tue, 17 Jul 2012 02:37:35 -0400 [thread overview]
Message-ID: <jwv1ukac2u8.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <01718D4EC241409DB101092AB41EAFA9@us.oracle.com> (Drew Adams's message of "Mon, 16 Jul 2012 22:50:16 -0700")
> Looking at your previous response, it seems to suggest only that the
> _call_ to `icicle-cmd2-after-load-bookmark+' would not be
> byte-compiled, because it is quoted.
Indeed. Compilation looks at the text, not at the dynamic call-tree, so
the code that's not textually inside a ' will be compiled just fine.
> But the defuns (via the macro) that are in the body of
> `icicle-cmd2-after-load-bookmark+': are they byte-compiled in the .elc
> where `icicle-cmd2-after-load-bookmark+' is defined?
Of course.
> IOW, given those messages, I'm wondering again whether I really need the
> (user-optional) calls to `icicle-maybe-byte-compile-after-load'. I was
> supposing that I needed them because the definitions are inside an
> `eval-after-load' (with a quoted sexp, as you mentioned).
No, the definitions are not inside an eval-after-load. They are
*evaluated* from an eval-after-load, but they are not *located*
inside it.
Stefan
next prev parent reply other threads:[~2012-07-17 6:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 3:28 bug#11847: 24.1.50; Error: Don't know how to compile #[nil "..."] Drew Adams
2012-07-03 6:12 ` Drew Adams
2012-07-03 6:21 ` Drew Adams
2012-07-03 13:42 ` Stefan Monnier
2012-07-03 14:44 ` Drew Adams
2012-07-03 17:26 ` Stefan Monnier
2012-07-03 18:00 ` Drew Adams
2012-07-05 15:49 ` Drew Adams
2012-07-05 16:14 ` Stefan Monnier
2012-07-05 16:20 ` Drew Adams
2012-07-17 5:56 ` Drew Adams
2012-07-17 5:50 ` Drew Adams
2012-07-17 6:37 ` Stefan Monnier [this message]
2012-07-17 6:40 ` 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=jwv1ukac2u8.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11847@debbugs.gnu.org \
--cc=drew.adams@oracle.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).