From: Drew Adams <drew.adams@oracle.com>
To: Heime <heimeborgia@protonmail.com>,
Michael Heerdegen <michael_heerdegen@web.de>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: Passing result of macroexpand-all as argument to a function
Date: Wed, 9 Aug 2023 15:27:01 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488FFE1DDC95FA3E5D7A6C9F312A@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <Iacr_zQ2fZMWLGM2c6RfpJBhtd8flyomcmDmDs-ywHDDALlSHZcXfYVDRJdd8AbGfErp9EkDYO1ShNN1vqNITrW26pi7HIfRgox7PoXfCQU=@protonmail.com>
> > Why don't you just try?
> I do not think one can just try it
Yes, you can. (This is the beauty of Lisp.)
> because it is not evident at what instance in
> time does the interpreter interpret the output
> code of a macro.
As mentioned, a macro _call_, such as (mymacro...)
is interpreted at that same time any Lisp form is.
What's particular about interpreting a macro call
is that first the call is macroexpanded, according
to the macro definition, and then the expansion
result is interpreted (evaluated) - immediately.
That's all.
If you byte-compile the Lisp source code then the
macro call gets macroexpanded during compilation,
and the result of expansion is then compiled to
produce the byte-compiled code. In effect, the
macro-call source code disappears and is replaced
by the expansion, in line, and the resulting code
is then byte-compiled.
next prev parent reply other threads:[~2023-08-09 15:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 0:22 Passing result of macroexpand-all as argument to a function Heime
2023-08-09 1:37 ` Pierre Rouleau
2023-08-09 2:04 ` Heime
2023-08-09 2:26 ` Corwin Brust
2023-08-09 2:40 ` Heime
2023-08-09 2:27 ` [External] : " Drew Adams
2023-08-09 2:53 ` Heime
2023-08-09 4:02 ` Pierre Rouleau
2023-08-09 4:14 ` Drew Adams
2023-08-09 3:37 ` Michael Heerdegen
2023-08-09 4:13 ` Heime
2023-08-09 4:36 ` Michael Heerdegen
2023-08-09 4:54 ` Heime
2023-08-09 15:21 ` Drew Adams
2023-08-09 4:28 ` Drew Adams
2023-08-09 3:39 ` Michael Heerdegen
2023-08-09 5:06 ` Heime
2023-08-09 15:27 ` Drew Adams [this message]
2023-08-09 20:34 ` [External] : " Heime
2023-08-09 21:24 ` Drew Adams
2023-08-09 21:32 ` Heime
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=SJ0PR10MB5488FFE1DDC95FA3E5D7A6C9F312A@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@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.