From: Achim Gratz <Stromeko@nexgo.de>
To: 14422@debbugs.gnu.org
Subject: bug#14422: 24.3; Eager Macro Expansion
Date: Sun, 26 May 2013 21:57:54 +0200 [thread overview]
Message-ID: <874ndph5tp.fsf@Rainer.invalid> (raw)
In-Reply-To: <87hahz82rh.fsf@Rainer.invalid>
Stefan Monnier writes:
> The defvar is only executed at run time (although it does have an
> effect at compile time, which is to tell the compiler that the variable
> will exist at run time).
>
> So using `ll' during the macro expansion is wrong.
That may well be a bug in the original code, although of course the
defvar is in a different file that has been loaded before the test
definition would expand the macro, so the expectation is that the symbol
should exist and have nil value when trying to run the tests.
> If you want `ll' to defined earlier, you can wrap it in
> `eval-and-compile' (tho it's better not to abuse it). I can't tell what
> solution I'd recommend in your case, since your distilled test case is
> "too distilled" to understand what it's trying to do.
I'll have to check again how things were supposed to have been
initialized in Org, but the assumption that the (no longer existing)
macro definitions made was clearly that the stand-in for the ll symbol
was pre-existing at macro expansion time. I'll try to re-create the
test case to match that behaviour and come back to you.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2013-05-26 19:57 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 [this message]
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
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=874ndph5tp.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=14422@debbugs.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 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.