From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Default lexical-binding to t
Date: Fri, 01 Nov 2024 08:55:56 -0400 [thread overview]
Message-ID: <jwv34kbf79m.fsf-monnier+emacs@gnu.org> (raw)
In bug#74145 I suggest that it is time to change the default of
`lexical-binding` to t. Clearly this is a breaking change, but only for
those files which:
- Don't have a `lexical-binding` cookie.
- Have code which happens to behave differently under the new dialect
(such code is not rare, but a lot of code works identically in the
two dialects).
I believe by the time Emacs-31 will be released, such files will be
uncommon, and it is easy to fix them (either by adjusting he code, or
by slapping a `lexical-binding` cookie).
Stefan
next reply other threads:[~2024-11-01 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 12:55 Stefan Monnier [this message]
2024-11-01 14:42 ` Default lexical-binding to t Gerd Möllmann
2024-11-01 17:03 ` Karl Fogel
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=jwv34kbf79m.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).