unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Lexical binding: why?
Date: Tue, 28 May 2019 13:58:38 -0400	[thread overview]
Message-ID: <jwvv9xutqlf.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 20190528174127.GC5296@ACM

> I was thinking more of a bug, since fixed, in older versions of the
> lexical-binding code.  Purely hypothetically at the moment, of course.
> But this code is surely not so simple that bugs can be ruled out.

Oh, so it's a hypothetical need.

> For consistency with other features, which can all be enabled
> conditionally, surely lexical-binding should also be conditionally
> enablable in a reasonable way.

Based on the 7 years of experience since Emacs-24.1 was released,
I think YAGNI is a good reason not to bother trying to implement it.

Especially since: if the file's content really does work when
lexical-binding is nil, then a simple workaround for the lack of this
feature is to keep using lexical-binding=nil until the problematic
version(s) are not supported any more and you can set
lexical-binding=t unconditionally.

While I do hope we'll be able to drop support for lexical-binding=nil in
some distant future, "distant" is an import characterization.  I'd be
amazed if this happened before 2030.


        Stefan




  reply	other threads:[~2019-05-28 17:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28 10:08 Lexical binding: why? Alan Mackenzie
2019-05-28 12:01 ` Tadeus Prastowo
2019-05-28 12:26 ` Stefan Monnier
2019-05-28 13:02   ` Dmitry Gutov
2019-05-28 13:25     ` Stefan Monnier
2019-05-28 13:46       ` Dmitry Gutov
2019-05-28 13:44   ` Alan Mackenzie
2019-05-28 17:21     ` Stefan Monnier
2019-05-28 17:41       ` Alan Mackenzie
2019-05-28 17:58         ` Stefan Monnier [this message]
2019-05-28 15:19 ` John Wiegley

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=jwvv9xutqlf.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).