From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: akrl@sdf.org, stefan@marxist.se, drew.adams@oracle.com,
emacs-devel@gnu.org
Subject: Re: "Bringing GNU Emacs to Native Code" at the European Lisp Symposium
Date: Fri, 01 May 2020 22:21:43 -0400 [thread overview]
Message-ID: <E1jUhmh-0005dp-8L@fencepost.gnu.org> (raw)
In-Reply-To: <jwvmu6t3cmk.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 29 Apr 2020 23:00:48 -0400)
[[[ 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. ]]]
> but I think it's perfectly OK to require using Elisp/l in order to
> make use of some new features. We already do that in various cases
> (e.g. `gv-ref`, `thunk.el`, `generator.el` and I'm sure there are
> others).
Those issues are not comparable to this issue. They are facilities
for use in code, and they have trouble with dynamic binding for
inherent reasons. Even in lexical binding mode, they may fail to work
as expected with code that binds dynamic variables.
None of that applies to a compiler. Any compiler that transforms Emacs Lisp
into something else must be able to deal with dynamic binding. So there is
no reason it should have trouble with dynamic binding mode, that only means
it is not finished.
--
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2020-05-02 2:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 17:11 "Bringing GNU Emacs to Native Code" at the European Lisp Symposium Stefan Kangas
2020-04-28 19:25 ` Andrea Corallo
2020-04-28 19:35 ` Amin Bandali
2020-04-28 20:06 ` Andrea Corallo
2020-04-28 21:13 ` Amin Bandali
2020-04-29 3:24 ` Richard Stallman
2020-04-29 18:47 ` Andrea Corallo
2020-04-28 19:36 ` tomas
2020-04-28 22:00 ` Drew Adams
2020-04-28 22:18 ` Stefan Monnier
2020-04-28 22:51 ` Drew Adams
2020-04-29 7:04 ` Eli Zaretskii
2020-04-29 12:38 ` Stefan Monnier
2020-04-29 14:02 ` Eli Zaretskii
2020-04-28 22:38 ` Dmitry Gutov
2020-04-29 10:55 ` Andrea Corallo
2020-04-29 15:35 ` Drew Adams
2020-04-29 18:57 ` Andrea Corallo
2020-04-29 19:29 ` Drew Adams
2020-04-30 1:14 ` Stefan Monnier
2020-04-30 2:27 ` Richard Stallman
2020-04-30 3:00 ` Stefan Monnier
2020-05-02 2:21 ` Richard Stallman [this message]
2020-05-02 13:43 ` Stefan Monnier
2020-04-30 20:32 ` Andrea Corallo
2020-05-02 2:27 ` Richard Stallman
2020-05-02 9:48 ` Andrea Corallo
2020-05-03 3:44 ` Richard Stallman
2020-05-03 4:28 ` Stefan Monnier
2020-05-04 3:09 ` Richard Stallman
2020-05-04 5:17 ` Stefan Monnier
2020-05-05 2:56 ` Richard Stallman
2020-05-05 3:18 ` Stefan Monnier
2020-05-04 10:07 ` Andrea Corallo
2020-05-02 13:50 ` 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=E1jUhmh-0005dp-8L@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=akrl@sdf.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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).