unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Simon Reiser <simonfxr@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Most of Elisp lacks lexical-binding: t
Date: Sat, 2 Feb 2019 14:54:23 +0000	[thread overview]
Message-ID: <20190202145423.GB1067@ACM> (raw)
In-Reply-To: <15a15e1c-c44b-b978-82f0-7bbb6b1b8ff1@googlemail.com>

Hello, Simon.

On Sat, Feb 02, 2019 at 13:35:03 +0100, Simon Reiser wrote:
>    Is there a reason, that out of ~1800 elisp files only 65 of them enable
>    lexical-bindings?

Yes, indeed.  Originally, Emacs Lisp only had dynamic binding, and
lexical binding is a relatively recent innovation.  It is work to
convert files to use lexical bindings, and so far nobody has put in this
work for most of the Lisp sources.

But by my count there are 551 out of 1528 files in the master branch
which have lexical binding enabled.  That's something over a third.

>    AFAIK lexical-binding allows for faster byte-code to be generated.
>    Maybe it would be a good idea to enable it in most of them and
>    document those files where it cannot be enabled.

My feeling is that most files could just be changed without problems,
but there will be enough exceptions that it needs to be done carefully.

Maybe it would be a good idea, but somebody(R) has got to step forward
and volunteer to do the work.  

>    Cheers,

>    Simon

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2019-02-02 14:54 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 [this message]
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
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=20190202145423.GB1067@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=simonfxr@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).