From: Steingold <sds@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Deprecating 'lexical-binding: nil'
Date: Thu, 30 Sep 2021 10:18:34 -0400 [thread overview]
Message-ID: <lzilyign9h.fsf@3c22fb11fdab.ant.amazon.com> (raw)
In-Reply-To: E1mVpA0-0004i1-KN@fencepost.gnu.org
> * Richard Stallman <ezf@tah.bet> [2021-09-30 02:03:12 -0400]:
>
> We should never remove nonlexical mode. To remove it would break old
> Emacs Lisp programs in a way that is very hard to fix. ...
> This would make old programs useless.
Not really.
I wrote elisp.lisp (http://clocc.hg.sourceforge.net/hgweb/clocc/clocc/raw-file/tip/src/cllib/elisp.lisp)
years ago to run ELisp code (that uses dynamic bindings)
under Common Lisp (that uses lexical bindings).
(The gist is to explicitly `declare` all variables `special`).
So, at the very least those old emacs lisp programs will still be
usable under CL.
--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1894
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://jihadwatch.org https://iris.org.il https://memri.org
nobody's life, liberty or property are safe while the legislature is in session
prev parent reply other threads:[~2021-09-30 14:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 22:47 Declaring 'lexical-binding: nil' obsolete Stefan Kangas
2021-09-25 23:17 ` Po Lu
2021-09-26 0:04 ` Stefan Kangas
2021-09-26 0:13 ` Po Lu
2021-09-26 0:50 ` Stefan Kangas
2021-09-26 1:20 ` Po Lu
2021-09-26 2:37 ` Stefan Kangas
2021-09-26 2:55 ` Po Lu
2021-09-26 6:30 ` Eli Zaretskii
2021-09-26 6:08 ` Eli Zaretskii
2021-09-26 6:06 ` Eli Zaretskii
2021-09-25 23:56 ` Eduardo Ochs
2021-09-26 0:35 ` Stefan Kangas
2021-09-26 6:02 ` Eli Zaretskii
2021-09-26 6:36 ` Lars Ingebrigtsen
2021-09-27 22:35 ` Deprecating 'lexical-binding: nil' Richard Stallman
2021-09-27 23:09 ` Stefan Kangas
2021-09-28 1:42 ` Stefan Monnier
2021-09-30 6:03 ` Richard Stallman
2021-09-30 14:18 ` Steingold [this message]
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=lzilyign9h.fsf@3c22fb11fdab.ant.amazon.com \
--to=sds@gnu.org \
--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).