unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: emacs-devel@gnu.org
Subject: Re: Most of Elisp lacks lexical-binding: t
Date: Mon, 04 Feb 2019 16:54:04 -0500	[thread overview]
Message-ID: <jwvwomfut3u.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87y36vzrhl.fsf@russet.org.uk> (Phillip Lord's message of "Mon, 04 Feb 2019 12:07:50 +0000")

> The question is, though, at what point does it become the default?

IIUC Eli is not in a hurry to see it become the default.

> One answer would be, support a "dynamic-binding" cookie line for
> Emacs-27 (which does nothing by default),

You can already use

    -*- lexical-binding:nil -*-

for that.

> incorporate your lexical-binding hack as an option.
> Then, go to lexical by default for Emacs-28.

This sounds rather optimistic to me.  We should at least start by giving
some warnings from the byte-compiler when compiling am Elisp file without
lexical-binding.  Maybe same thing when visiting an Elisp file.

There are also all the calls to `eval` which currently tend to mostly
still use dynamic binding (even in files labeled with
lexical-binding:t).  E.g. we could advertise `eval` as taking a minimum
of 2 args so the byte-compiler would start warning about calls that
don't explicitly request lexical or dynamic binding (and hence fall
back to the default dynamic binding).


        Stefan



  reply	other threads:[~2019-02-04 21: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
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 [this message]
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=jwvwomfut3u.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --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).