From: Tony Day <zygomega@gmail.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: emacs devel <emacs-devel@gnu.org>
Subject: Re: emacs roadmap
Date: Tue, 18 Dec 2012 11:02:38 +1100 [thread overview]
Message-ID: <41948E36-E9AB-40F0-8D08-282C7040B2E8@gmail.com> (raw)
In-Reply-To: <CA+U71=PVnojYOXHpgZrVWJFPNzUF7cC8ALPAQTNNn4zz52Jx3g@mail.gmail.com>
On 17 Dec 2012, at 09:37, Noah Lavine <noah.b.lavine@gmail.com> wrote:
> Guile used to be an embeddable implementation of the Scheme programming language, and there was a plan to use Guile in Emacs and rewrite everything in Guile. Guile (since 2.0) is now an embeddable VM and a collection of compilers to that VM. It can run Elisp in the same way that Emacs can.
Thanks - that helps tremendously. I was mixing up old-school discussions of guile with Guile 2.0. Lua support coming - wow!
> There has been talk of using the Guile VM in Emacs.
>
Where would that talk be located?
> As for realism - it's certainly a realistic possibility technically. The work would mostly be in the C part of Emacs - changing lisp.h, the interpreter, and similar things. The low-level Elisp that implements the compiler would also change, but almost all Elisp would be untouched. There would be some technical advantages, and I can think of one possible technical downside. (I'll write more about those if anyone's interested.)
I'd be very interested in your views of both the advantages and disadvantages, for one.
next prev parent reply other threads:[~2012-12-18 0:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 22:25 emacs roadmap Tony Day
2012-12-16 22:37 ` Noah Lavine
2012-12-18 0:02 ` Tony Day [this message]
2012-12-17 2:36 ` Stefan Monnier
2012-12-18 1:36 ` Tony Day
2012-12-18 4:02 ` Stefan Monnier
2012-12-17 18:49 ` Tom Tromey
2012-12-18 0:05 ` Tony Day
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=41948E36-E9AB-40F0-8D08-282C7040B2E8@gmail.com \
--to=zygomega@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=noah.b.lavine@gmail.com \
/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.