unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
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 10:20:03 -0500	[thread overview]
Message-ID: <10414fb8-e09c-a4fa-dcd1-5ccfff10650d@gmail.com> (raw)
In-Reply-To: <jwvbmgb3nhc.fsf-monnier+emacs@gnu.org>

On 2018-02-26 08:11, Stefan Monnier wrote:
>>> This is not supposed to work: your test.el uses `mmm` before it gets
>>> defined by the subsequent `load`.
>> Uh, really? But the body of with-eval-after-load is (supposed to be)
>> evaluated after the FILE argument is loaded, not before, right?  `mmm'
>> is only used in `with-eval-after-load' in the code above.
> 
> The time of evaluation doesn't matter.  Think of the case where we
> *compile* the file.

Why is that relevant here, given that I'm *not* compiling the file?
(FWIW, I do indeed expect with-eval-after-load to protect its argument from compilation, yes.  Is it documented not to?)




  reply	other threads:[~2018-02-26 15:20 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 [this message]
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

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=10414fb8-e09c-a4fa-dcd1-5ccfff10650d@gmail.com \
    --to=cpitclaudel@gmail.com \
    --cc=emacs-devel@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).