From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 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:38:55 -0500 [thread overview]
Message-ID: <jwvvaej64g6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <9100fb65-a95a-0678-68fa-7d615d481284@gmail.com> ("Clément Pit-Claudel"'s message of "Mon, 26 Feb 2018 12:15:25 -0500")
>> | (test-macro
>> | #[0 #1="byte code..."
>> | [(lambda nil
>> | (let
>> | ((out
>> | (mmm
>> | #'(lambda nil nil))))
>> | (message "with-eval-after-load: %S" out)))
>> | ...]
>> | 11])
>
> Right, I think that's broken.
Yes, at that time it's already too late.
>> Maybe you can change `mmm' so that it handles both of these cases as you
>> want?
> We're considering this for Flycheck, yup :)
That won't help the case where the code was compiled. You really need
to think in terms of compilation: people generally don't have a clear
idea of when macroexpansion takes place for interpreted code, whereas
it's clearer in the case the code is compiled.
> Mostly though, I'd like to understand where the issue comes from (my current
> understanding is that it's a miscompilation), and whether it can be fixed.
That's right, it gets miscompiled because the compiler isn't told about
the `mmm` macro beforehand so it presumes that it's an unknown function.
Stefan
prev parent reply other threads:[~2018-02-26 17:38 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
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 [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=jwvvaej64g6.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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.