From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: What's the point of byte-compile-define-keymap?
Date: Sat, 27 Nov 2021 16:36:47 +0000 [thread overview]
Message-ID: <YaJen7lrhOwNMEjW@ACM> (raw)
Hello, Emacs.
It looks to me that byte-compile-define-keymap (in
lisp/emacs-lisp/bytecomp.el) saves its FORM argument in ORIG-FORM and
always returns it unchanged. This looks like an oversight.
Also, would this function not better be named
byte-compile-FILE-FORM-define-keymap, since it is the value of a
byte-hunk-handler symbol property.
Also[2], is this function really necessary? Is define-keymap used
sufficiently often to justify a special byte-hunk-handler for it?
--
Alan Mackenzie (Nuremberg, Germany).
next reply other threads:[~2021-11-27 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 16:36 Alan Mackenzie [this message]
2021-11-28 13:30 ` What's the point of byte-compile-define-keymap? Lars Ingebrigtsen
2021-11-28 13:43 ` Stefan Monnier
2021-11-28 13:45 ` Lars Ingebrigtsen
2021-11-28 17:15 ` Mattias Engdegård
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=YaJen7lrhOwNMEjW@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.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).