Subject: Re: bug#46958: 28.0.50; invalid-function error for macros that have function bindings

From: Pip Cet <[email-masked]>
Date: Sun, 7 Mar 2021 18:06:37 +0000

On Sun, Mar 7, 2021 at 3:58 PM Lars Ingebrigtsen <[email-masked]> wrote:
> Pip Cet <[email-masked]> writes:
> > On Sat, Mar 6, 2021 at 12:56 PM Lars Ingebrigtsen <[email-masked]> wrote:
> >> The other issue is that I think there's a misunderstanding here: You can
> >> never funcall a macro.
> >
> > You shouldn't be able to, but I don't think bug#46636 has been fixed.
>
> That's not a bug about funcalling macros,

Funny, that's precisely what it sounds like to me.

> but about M-: using
> `macroexpand-all' before evaluating, isn't it?

That's where the bug is, yes, but together with the analogous byte
optimizer bug it means that all of the usual ways of evaluating
(funcall #'when t) will succeed. That means you can funcall macros, in
my book.

Pip