unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: phillip.lord@russet.org.uk,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: Most of Elisp lacks lexical-binding: t
Date: Tue, 05 Feb 2019 18:37:55 +1300	[thread overview]
Message-ID: <b6f2ec70ecfd32c6d1d632cea2afdd52@webmail.orcon.net.nz> (raw)
In-Reply-To: <83zhraud00.fsf@gnu.org>

On 2019-02-05 16:31, Eli Zaretskii wrote:
> I don't see how we could make this the default before we complete
> converting all the Lisp files to lexical binding (or, unlikely, decide
> that some of them need to use dynamic binding).  It would mean risking
> a lot of breakage.

And that's not just for Emacs core -- there is a massive quantity of
elisp in the ecosystem at large which was not written for lexical
binding, and still works absolutely fine in current versions of Emacs.
Such libraries might well no longer have a maintainer (but at present
not be in any need of one).

Releasing a "lexical-binding by default" version of Emacs would surely
create a substantial risk of many user's configs failing on them in a
variety of ways when they upgrade, and suddenly needing a lot of
effort to get working (which for some users will be outside of their
skill set).

The risk seems rather high to me.  I'm not sure the reward would be
worth it?  (When the reward would seem to be nothing more than library
authors being able to omit -*- lexical-binding: t; -*- which, even if
it looks untidy, isn't exactly an onerous requirement).


-Phil




  reply	other threads:[~2019-02-05  5:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-02 12:35 Most of Elisp lacks lexical-binding: t Simon Reiser
2019-02-02 14:54 ` Alan Mackenzie
2019-02-04  1:36   ` Stefan Monnier
2019-02-04  3:46     ` T.V Raman
2019-02-04 12:07     ` Phillip Lord
2019-02-04 21:54       ` Stefan Monnier
2019-02-05  3:31         ` Eli Zaretskii
2019-02-05  5:37           ` Phil Sainty [this message]
2019-02-05 14:00             ` Stefan Monnier
2019-02-06 19:59               ` Phillip Lord
2019-02-06 22:47                 ` Stefan Monnier
2019-02-07 16:41                   ` Paul Eggert
2019-02-08  3:31                     ` Stefan Monnier
2019-02-05 13:48           ` Stefan Monnier
2019-02-06  6:58         ` Richard Stallman
2019-02-06 14:02           ` Stefan Monnier

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=b6f2ec70ecfd32c6d1d632cea2afdd52@webmail.orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=phillip.lord@russet.org.uk \
    /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).