From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 44854@debbugs.gnu.org
Subject: bug#44854: [PATCH] Add lexical-binding cookie to autoload files
Date: Sat, 28 Nov 2020 09:59:06 +0200 [thread overview]
Message-ID: <834kl9oqt1.fsf@gnu.org> (raw)
In-Reply-To: <868samwhk0.fsf@gmail.com> (message from Andy Moreton on Fri, 27 Nov 2020 22:39:27 +0000)
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Fri, 27 Nov 2020 22:39:27 +0000
>
> If adding a lexical-binding tag has no effect on the autoload files
> (other than making them a few bytes larger), then it should be of no
> consequence.
The additional code in autoload.el is such a consequence, if nothing
else.
> Adding the tag to the autoloads is not about needing code changes, but
> simply a marker that those files are ready for the flip-the-switch
> event.
They are already ready for the flip.
> However, by treating all .el files uniformly (including autoloads), it
> makes it easier to write scripts that check for lexical binding support
> in source files.
That is an advantage too small to justify the change. Skipping files
that all match a simple wildcard pattern is easy. We will always need
to skip some files anyway, for example .dir-locals.el.
It makes no sense to me, sorry.
next prev parent reply other threads:[~2020-11-28 7:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 19:34 bug#44854: [PATCH] Add lexical-binding cookie to autoload files Stefan Kangas
2020-11-24 20:21 ` Eli Zaretskii
2020-11-24 20:46 ` Stefan Kangas
2020-11-24 20:54 ` Drew Adams
2020-11-24 21:05 ` Stefan Kangas
2020-11-24 21:22 ` Drew Adams
2020-11-24 21:57 ` Stefan Monnier
2020-11-24 22:39 ` Drew Adams
2020-11-24 21:04 ` Eli Zaretskii
2020-11-24 21:35 ` Stefan Kangas
2020-11-24 21:43 ` Drew Adams
2020-11-25 7:23 ` Lars Ingebrigtsen
2020-11-25 15:02 ` Eli Zaretskii
2020-11-25 15:08 ` Lars Ingebrigtsen
2020-11-25 16:40 ` Stefan Monnier
2020-11-25 17:30 ` Eli Zaretskii
2020-11-25 17:54 ` Stefan Monnier
2020-11-25 18:22 ` Eli Zaretskii
2020-11-25 18:56 ` Stefan Monnier
2020-11-25 19:01 ` Philipp Stephani
2020-11-25 19:15 ` Eli Zaretskii
2020-11-25 19:12 ` Eli Zaretskii
2020-11-25 19:35 ` Philipp Stephani
2020-11-25 20:00 ` Eli Zaretskii
2020-11-25 20:06 ` Stefan Monnier
2020-11-25 20:27 ` Eli Zaretskii
2020-11-25 21:07 ` Stefan Kangas
2020-11-26 14:02 ` Eli Zaretskii
2020-11-27 22:39 ` Andy Moreton
2020-11-28 7:59 ` Eli Zaretskii [this message]
2020-11-29 10:30 ` Lars Ingebrigtsen
2020-12-02 13:51 ` Stefan Kangas
2020-11-25 20:53 ` Stefan Kangas
2020-11-24 20:24 ` Drew Adams
2020-11-24 21:05 ` Stefan Kangas
2020-11-24 21:28 ` Drew Adams
2020-11-24 21:58 ` Stefan Monnier
2020-12-31 5: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=834kl9oqt1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44854@debbugs.gnu.org \
--cc=andrewjmoreton@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).