From: Pip Cet <pipcet@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Naoya Yamashita <conao3@gmail.com>, emacs-devel@gnu.org
Subject: Re: [PATCH] * src/eval.c: Stop checking for nvars, and use only CONSP
Date: Tue, 2 Mar 2021 15:19:14 +0000 [thread overview]
Message-ID: <CAOqdjBcJfd5VfwFjDkPLuh4CWevLu0sFBg1U7TipVTu4DeLPHQ@mail.gmail.com> (raw)
In-Reply-To: <jwvblc1my3g.fsf-monnier+emacs@gnu.org>
On Tue, Mar 2, 2021 at 2:32 PM Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> I view the ELisp interpreter as a crutch to bootstrap the system.
Well, I view the bytecode compiler as a crutch to get to LIMPLE for
native compilation ;-)
I'm all for a revolution, but it might be a bit early to chop off this
particular king's head...
> AFAIK the only really good reason why we still have it is for the
> benefit of debugging: debugging byte-compiled code (whether with Edebug
> or with the backtrace debugger) is a lot more constraining than
> debugging interpreted code, mostly because it loses the information
> about the currently bound lexical variables.
> All other uses of it could
> be replaced by something like
>
> (defun eval (exp) (funcall (byte-compile `(lambda () ,exp))))
Except for the ones that can't. ELC is still limited to 64K constants
in the vector, for example, isn't it? It's a bit late in the century
for 16-bit limits...
But as for the original question, do we have to have Flet? I just
defined a macro called let which builds a closure and calls it, and it
crashed my Emacs. But if it would work, could we get rid of this
entire (C) function?
Oh, right, I assumed lexical scoping...
Pip
next prev parent reply other threads:[~2021-03-02 15:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 2:10 [PATCH] * src/eval.c: Stop checking for nvars, and use only CONSP Naoya Yamashita
2021-03-02 2:48 ` Stefan Monnier
2021-03-02 3:09 ` Naoya Yamashita
2021-03-02 14:31 ` Stefan Monnier
2021-03-02 15:19 ` Pip Cet [this message]
2021-03-02 15:48 ` Stefan Monnier
2021-03-02 17:04 ` Pip Cet
2021-03-02 17:44 ` Stefan Monnier
2021-03-02 19:50 ` Pip Cet
2021-03-02 23:48 ` Stefan Monnier
2021-03-02 5:34 ` Pip Cet
2021-03-02 5:41 ` Eli Zaretskii
2021-03-02 7:14 ` Naoya Yamashita
2021-03-02 7:30 ` Pip Cet
2021-03-02 14:00 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOqdjBcJfd5VfwFjDkPLuh4CWevLu0sFBg1U7TipVTu4DeLPHQ@mail.gmail.com \
--to=pipcet@gmail.com \
--cc=conao3@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.