From: Pierre Rouleau <prouleau001@gmail.com>
To: Heime <heimeborgia@protonmail.com>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Passing result of macroexpand-all as argument to a function
Date: Tue, 8 Aug 2023 21:37:39 -0400 [thread overview]
Message-ID: <CALTqLiaX=5LPOEB_rfBGX3+TmKC3ZRrHxSM-X7KWwgZpXeYc5A@mail.gmail.com> (raw)
In-Reply-To: <wfjZtOOVuhuQ61fghs8SFtJiAHoEMmnTGwaGutw-ZdB3Yh5KrJsocuL1V-AfUkdmk2-gD0aH_2paux_91KVpPWhHDPuLDTEv8xDCKD-seQU=@protonmail.com>
On Tue, Aug 8, 2023 at 8:22 PM Heime <heimeborgia@protonmail.com> wrote:
> If I want to pass the result of a macro without final evaluation as
> argument
> to a function, what kind of structure will it be ?
>
> I would be using
>
> (macroexpand-all (this-macro arg))
>
> which I would pass as argument to a function.
>
> 1- What is the problem that you are trying to solve?
2- If you want to pass something to a function and you want that something
not evaluated, then: quote it. The function can later evaluate it if it
needs to extract the result of the expression, or it can print it using a
string formatting function.
3- If #2 is not clear, reading a LISP tutorial will help. Investing time
reading on LISP and Emacs Lisp will help a lot.
--
/Pierre
next prev parent reply other threads:[~2023-08-09 1:37 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 [this message]
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 ` [External] : " Drew Adams
2023-08-09 20:34 ` 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
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='CALTqLiaX=5LPOEB_rfBGX3+TmKC3ZRrHxSM-X7KWwgZpXeYc5A@mail.gmail.com' \
--to=prouleau001@gmail.com \
--cc=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@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.
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).