unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Pip Cet <pipcet@gmail.com>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 46636@debbugs.gnu.org, Andreas Schwab <schwab@linux-m68k.org>
Subject: bug#46636: 28.0.50; M-: (funcall #'or) doesn't throw an error
Date: Fri, 19 Feb 2021 18:10:26 +0000	[thread overview]
Message-ID: <CAOqdjBemB0duZtk1zcCmWkGVe1G-tswiQ21idpATAZnx5RuEJA@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkRxYGCUsmtTudbeo_T0UZBGKZ4Z2+3m3cBcEr4MNx2USQ@mail.gmail.com>

On Fri, Feb 19, 2021 at 4:46 PM Philipp Stephani <p.stephani2@gmail.com> wrote:
> Am Fr., 19. Feb. 2021 um 15:03 Uhr schrieb Andreas Schwab
> <schwab@linux-m68k.org>:
> >
> > On Feb 19 2021, Pip Cet wrote:
> >
> > > Recipe starting from emacs -Q:
> > >
> > > M-: (funcall #'or) RET
> >
> > If you want authentic results, use ielm, not eval-expression.
>
> Ah, so the rewrite that macroexpand-all (in macroexp--expand-all)
> performs is the culprit here.

Yes, I think so.

> Maybe it should only rewrite if the
> first argument is indeed a function, or an autoload of a function?

I'm unconvinced it's worth it at all to rewrite funcalls or applys,
either in macroexp or in the byte compiler.

But if we have to, we have to make sure (apply #'or nil) and (funcall
#'or) are rejected somewhere (maybe as early as the #').





  reply	other threads:[~2021-02-19 18:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 13:26 bug#46636: 28.0.50; M-: (funcall #'or) doesn't throw an error Pip Cet
2021-02-19 13:35 ` Lars Ingebrigtsen
2021-02-19 14:01 ` Andreas Schwab
2021-02-19 16:46   ` Philipp Stephani
2021-02-19 18:10     ` Pip Cet [this message]
2021-02-19 18:28 ` bug#46636: [External] : " Drew Adams
2021-02-22  6:20   ` Richard Stallman
2021-02-22  8:25     ` Andreas Schwab
2021-02-22  9:16       ` Pip Cet
2021-02-22  8:41     ` Pip Cet
2022-06-17 17:39 ` Lars Ingebrigtsen

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=CAOqdjBemB0duZtk1zcCmWkGVe1G-tswiQ21idpATAZnx5RuEJA@mail.gmail.com \
    --to=pipcet@gmail.com \
    --cc=46636@debbugs.gnu.org \
    --cc=p.stephani2@gmail.com \
    --cc=schwab@linux-m68k.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. 
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).