From: Eli Zaretskii <eliz@gnu.org>
To: Akib Azmain Turja <akib@disroot.org>
Cc: tumashu@163.com, 59793@debbugs.gnu.org
Subject: bug#59793: 29.0.60; subr.elc is not compiled correctly
Date: Sun, 04 Dec 2022 19:00:02 +0200 [thread overview]
Message-ID: <83o7sj9ka5.fsf@gnu.org> (raw)
In-Reply-To: <87zgc31kov.fsf@disroot.org> (message from Akib Azmain Turja on Sun, 04 Dec 2022 17:18:24 +0600)
> From: Akib Azmain Turja <akib@disroot.org>
> Cc: tumashu@163.com, 59793@debbugs.gnu.org
> Date: Sun, 04 Dec 2022 17:18:24 +0600
>
> > I understand you didn't expect the result of cl-letf*, and were surprised by
> > what you saw, but I don't understand why you expect the Emacs development to
> > do something about your surprise.
> >
>
> With subr.el (source), the bug59793-yank function overrides
> 'insert-for-yank' successfully.
>
> With subr.elc (compiled byte-code), the function can't override
> 'insert-for-yank'. Just try to replace the 'cl-letf' (not 'cl-letf*')
> form with an 'error' call, bug59793-yank still just inserts text, which
> is, obviously, unexpected.
Yes, I understand.
> > See above: I understand what you are saying, but not why this is submitted
> > as a bug to the Emacs development team.
>
> Both source and compiled Emacs Lisp code should show the same behavior,
> except performance.
No, not when you replace the function's definition with the likes of
cl-letf.
> But 'subr.el' and 'subr.elc' show different behaviors. Isn't this a
> byte-compiler bug?
No.
next prev parent reply other threads:[~2022-12-04 17:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 7:24 bug#59793: 29.0.60; subr.elc is not compiled correctly Feng Shu
2022-12-03 9:55 ` Eli Zaretskii
2022-12-03 15:10 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-03 15:37 ` Eli Zaretskii
2022-12-03 17:16 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-03 18:10 ` Eli Zaretskii
2022-12-03 21:49 ` Feng Shu
2022-12-04 7:08 ` Eli Zaretskii
2022-12-04 11:21 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 17:01 ` Eli Zaretskii
2022-12-04 18:56 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 19:17 ` Eli Zaretskii
2022-12-09 10:44 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-09 19:18 ` Eli Zaretskii
2022-12-10 6:09 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-10 8:26 ` Eli Zaretskii
2022-12-10 7:32 ` Visuwesh
2022-12-10 8:30 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 11:18 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 17:00 ` Eli Zaretskii [this message]
2022-12-04 17:27 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 17:35 ` Eli Zaretskii
2023-09-10 19:26 ` Stefan Kangas
2022-12-04 18:52 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-03 17:48 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-03 17:50 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-03 21:50 ` Feng Shu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o7sj9ka5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59793@debbugs.gnu.org \
--cc=akib@disroot.org \
--cc=tumashu@163.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.