From: Pip Cet <pipcet@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Robert Irelan <rirelan@gmail.com>, 46958@debbugs.gnu.org
Subject: bug#46958: 28.0.50; invalid-function error for macros that have function bindings
Date: Sun, 7 Mar 2021 18:06:37 +0000 [thread overview]
Message-ID: <CAOqdjBd8_XLVbiBTnGmX-0gVK9Z60sTSY-_azwNjkcE9TADgcw@mail.gmail.com> (raw)
In-Reply-To: <877dmjnef9.fsf@gnus.org>
On Sun, Mar 7, 2021 at 3:58 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Pip Cet <pipcet@gmail.com> writes:
> > On Sat, Mar 6, 2021 at 12:56 PM Lars Ingebrigtsen <larsi@gnus.org> 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
prev parent reply other threads:[~2021-03-07 18:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 2:00 bug#46958: 28.0.50; invalid-function error for macros that have function bindings Robert Irelan
2021-03-06 12:55 ` Lars Ingebrigtsen
2021-03-06 14:24 ` Basil L. Contovounesios
2021-03-06 18:28 ` Robert Irelan
2021-03-06 22:39 ` Phil Sainty
2021-03-07 14:27 ` Basil L. Contovounesios
2021-03-07 21:38 ` Robert Irelan
2021-03-08 6:30 ` Phil Sainty
2021-03-08 7:18 ` Robert Irelan
2021-03-08 9:06 ` Phil Sainty
2022-06-20 1:10 ` Lars Ingebrigtsen
2021-03-07 14:33 ` Pip Cet
2021-03-07 15:58 ` Lars Ingebrigtsen
2021-03-07 18:06 ` Pip Cet [this message]
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=CAOqdjBd8_XLVbiBTnGmX-0gVK9Z60sTSY-_azwNjkcE9TADgcw@mail.gmail.com \
--to=pipcet@gmail.com \
--cc=46958@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rirelan@gmail.com \
/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).