From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: 14422@debbugs.gnu.org
Subject: bug#14422: 24.3; Eager Macro Expansion
Date: Thu, 30 May 2013 17:14:56 -0400 [thread overview]
Message-ID: <jwvd2s841gz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ehcojm1e.fsf@Rainer.invalid> (Achim Gratz's message of "Thu, 30 May 2013 21:38:21 +0200")
retitle 14422 Apply eager-macroexpansion everywhere (eval-region, ...)
thanks
> The remaining point is that the ERT test still fails in exactly the same
> way when it is _not_ byte-compiled and batch-tested (like the original
> case in Org), but it produces the correct result when testing in
> interactive mode or in the debugger. I guess I'm asking for a warning
> for recursive macro expansions that manipulate the same variable both at
> expansion and at runtime in separate macros. Alternatively if the buggy
> code would always fail in the same way that would at least ensure it can
> be found more easily.
Indeed, that's part of the reason why I introduced this "eager
macroexpansion", which makes it that my previous foo.el test now behaves
identically whether it's byte-compiled or not.
The behavior is still different in a few other cases (where eager macro
expansion is not performed, typically M-C-x and things like that), but
I hope to reduce/eliminate them at some point.
Stefan
next prev parent reply other threads:[~2013-05-30 21:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 14:26 bug#14422: 24.3; Eager Macro Expansion Achim Gratz
2013-05-21 2:11 ` Stefan Monnier
2013-05-26 15:34 ` Achim Gratz
2013-05-26 19:29 ` Stefan Monnier
2013-05-26 19:57 ` Achim Gratz
2013-05-30 17:59 ` Achim Gratz
2013-05-30 19:00 ` Stefan Monnier
2013-05-30 19:38 ` Achim Gratz
2013-05-30 21:14 ` Stefan Monnier [this message]
2013-06-03 15:29 ` Stefan Monnier
2020-08-25 11:05 ` Lars Ingebrigtsen
2020-10-13 1:47 ` Lars Ingebrigtsen
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=jwvd2s841gz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=14422@debbugs.gnu.org \
--cc=Stromeko@nexgo.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.