unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org, phillip.lord@russet.org.uk
Subject: Re: Most of Elisp lacks lexical-binding: t
Date: Wed, 06 Feb 2019 01:58:56 -0500	[thread overview]
Message-ID: <E1grHAe-0005b0-U2@fencepost.gnu.org> (raw)
In-Reply-To: <jwvwomfut3u.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 04 Feb 2019 16:54:04 -0500)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

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

Perhaps it would be better to define a new function, perhaps
`eval-lexically', for specifying a lexical context.
If these calls need to be changed anyway, changing the function name
is no extra work.  And the changed function name will make it
easy to search for what has or has not been changed.

We also need to keep track of which calls to eval should not be
changed.  There are various ways to do that -- for instance, we could
label files that contain calls to eval when all those calls have been
checked.  Or we could define a new name, `eval-dynamically', to use in
calls which people have verified should not be changed.

Let's choose a way and start using it.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  parent reply	other threads:[~2019-02-06  6:58 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
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 [this message]
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=E1grHAe-0005b0-U2@fencepost.gnu.org \
    --to=rms@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).