Re: [External] : Re: Passing result of macroexpand-all as argument to a function

[Heime <heimeborgia@protonmail.com>]

Sent with Proton Mail secure email.

------- Original Message -------
On Wednesday, August 9th, 2023 at 4:36 PM, Michael Heerdegen <michael_heerdegen@web.de> wrote:


> Heime heimeborgia@protonmail.com writes:
> 
> > So in practice, is it needed to quote or not the result of
> > (macroexpand-all something arg) ?
> 
> 
> The result of the `macroexpand-all' call is an expression (i.e. a list
> most the time). Just a normal list that happens to look like and being
> usable as code.

Not according to Drew, who says I got to quote.

In other words, you are saying that macroexpand-all gives me just a normal list 
which is not evaluated before being passed to the function. Correct ?  

And then having a function defined as so

(defun myfunc (expr bfname)

and calling 

(myfunc (macroexpand-all something arg) bfname)

will handle bfname properly.  It will not pick up anything from
the macroexpand-all data.  Am I right ?

> So unless you want 'EXPR instead of EXPR you don't need to quote: the
> result will not be evaluated (unless it's the returned expansion of a
> macro call, but then you want the evaluation).

I am doing (pp-to-string expr) inside

(defun myfunc (expr bfname)
  (apply 'talos (list (pp-to-string expr) bfname)))
 
> As I said, why don't you try?

I tried it, but then others claimed it was not good doing. 
 
> Michael.