From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: A combination of defmacro, functionp, and quoted lambdas yields different results on consecutive evaluations
Date: Mon, 26 Feb 2018 12:13:23 -0500 [thread overview]
Message-ID: <jwv7eqz7kb6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <555f3f1b-d31f-ec12-e460-8b0c20816d45@gmail.com> ("Clément Pit-Claudel"'s message of "Mon, 26 Feb 2018 12:01:50 -0500")
> My user's problem is the following: Flycheck defines a macro that lets
> you define a new checker. One of our users wrote something like this:
>
> (with-eval-after-load 'flycheck
> (flycheck-define-checker
> …))
>
> This doesn't work. I claim that it should, or that it should be
> documented to not work. Do you disagree?
I think it is or should be documented, indeed, but not in
`with-eval-after-load` since this applies to everything else as well.
If you need to use a macro that's in file `foo`, then AFAIK you have
2 options:
- (require 'foo), either directly or transitively.
- hide your macro call behind a quote so it can't be compiled before
`foo` is loaded (regardless of whether you do compile or not
irrelevant: the right way to think about it is "what happens when it
gets compiled").
> Because of the documentation says that this macro arranges for evaluation to
> be delayed.
But macro expansion can take place long before evaluation.
E.g. `defun` also delays evaluation of its body. But
(defun foo ()
... (mmm blabla) ...)
(defmacro mmm (...) ...)
will suffer from the same problem (tho at least in this particular
case, the byte-compiler will notice and emit a warning, IIRC).
Stefan
next prev parent reply other threads:[~2018-02-26 17:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 16:04 A combination of defmacro, functionp, and quoted lambdas yields different results on consecutive evaluations Clément Pit-Claudel
2018-02-17 21:58 ` Stefan Monnier
2018-02-18 15:17 ` Clément Pit-Claudel
2018-02-18 18:02 ` Stefan Monnier
2018-02-25 18:09 ` Clément Pit-Claudel
2018-02-26 3:18 ` Stefan Monnier
2018-02-26 5:40 ` Clément Pit-Claudel
2018-02-26 13:11 ` Stefan Monnier
2018-02-26 15:20 ` Clément Pit-Claudel
2018-02-26 16:31 ` Stefan Monnier
2018-02-26 16:38 ` Stefan Monnier
2018-02-26 17:08 ` Clément Pit-Claudel
2018-02-26 17:31 ` Stefan Monnier
2018-02-28 14:32 ` Clément Pit-Claudel
2018-02-28 16:02 ` Stefan Monnier
2018-02-26 17:01 ` Clément Pit-Claudel
2018-02-26 17:13 ` Stefan Monnier [this message]
2018-02-26 17:32 ` Clément Pit-Claudel
2018-02-26 17:40 ` Clément Pit-Claudel
2018-03-01 0:50 ` Radon Rosborough
2018-02-27 21:35 ` Stefan Monnier
2018-02-28 12:44 ` Michael Heerdegen
2018-02-28 13:31 ` Stefan Monnier
2018-02-28 14:26 ` Clément Pit-Claudel
2018-02-28 23:12 ` Stefan Monnier
2018-02-26 13:13 ` Stefan Monnier
2018-02-26 15:20 ` Clément Pit-Claudel
2018-02-26 16:33 ` Stefan Monnier
2018-02-26 16:37 ` Michael Heerdegen
2018-02-26 17:15 ` Clément Pit-Claudel
2018-02-26 17:38 ` Stefan Monnier
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=jwv7eqz7kb6.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cpitclaudel@gmail.com \
--cc=emacs-devel@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 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).