From: Achim Gratz <Stromeko@nexgo.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 14422@debbugs.gnu.org
Subject: bug#14422: 24.3; Eager Macro Expansion
Date: Sun, 26 May 2013 17:34:10 +0200 [thread overview]
Message-ID: <87obbxhi19.fsf@Rainer.invalid> (raw)
In-Reply-To: <jwvzjvpm6cq.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 20 May 2013 22:11:15 -0400")
Stefan Monnier writes:
>> The following test case demonstrates a problem that has been distilled
>> from Org's test suite.
>
> % emacs24 -Q --batch -f batch-byte-compile eme.el
>
> In toplevel form:
> eme.el:3:1:Warning: global/dynamic var `ll' lacks a prefix
> eme.el:13:1:Error: Symbol's value as variable is void: ll
> %
>
> So the code has a problem, since byte-compiling it doesn't work
The code isn't meant to be byte-compiled, but if you want to I'd have to
split it into two seperate files. The ERT portion of the code is never
byte-compiled in Org and I don't know if it would make sense to do this.
> (emacs24 is 24.1, here). No wonder eager macro-expansion also leads
> to problems.
Well, the code does declare the variable symbol special and initializes
it nil, so finding the symbol undefined during compilation and/or macro
expansion would constitute a bug in either ERT or Emacs, no?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2013-05-26 15:34 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 [this message]
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
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
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=87obbxhi19.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=14422@debbugs.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).