[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs Lisp's future (was: Guile emacs thread (again))

From: Tom
Subject: Re: Emacs Lisp's future (was: Guile emacs thread (again))
Date: Wed, 17 Sep 2014 11:01:13 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

Lally Singh <lally.singh <at> gmail.com> writes:

> So if this a runtime system issue, what about elisp on LLVM?  Let the LLVM
project handle the backend and performance issues, and emacs can maintain
one language frontend.  There are plenty of people working on that, so emacs
can ride that for almost free.

In the long run this would be the most practical solution. Choosing
a well supported and widely used VM which gets  tons of developer 
attention, so the VM development would be taken care of, 
and Elisp could be implemented as a frontend.

This approach has the advantage of supporting the existing Elisp code
base and it would also make it possible to use other languages to extend
emacs, because widdely used VMs have frontend implementations for
many modern languages (Python, etc.)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]