3 ms·
> Once it is integrated into Emacs, Emacs will become Guile's killer app, boost its popularity and set it apart from other schemes. You say that like Guile be
by quotemstr 13y ago
> Once it is integrated into Emacs, Emacs will become Guile's killer app, boost its popularity and set it apart from other schemes.
You say that like Guile becoming the Emacs Lisp runtime is a foregone conclusion. It's not. The Emacs Lisp interpreter is so tightly bound to the C core (which uses lisp primitives for error handling, memory allocation, and data storage) that ripping it would involve massive modifications to large parts of that core.
Even if Guile were included in Emacs, it would be running Emacs Lisp almost all the time, not Scheme. Elisp, being a Lisp-2, is much closer to Common Lisp than it is to Scheme, and the recent integration of the cl-lib package has brought it even closer. We even have a CLOS workalike.
Embedding Guile in Emacs is a waste of time and energy. There are many desperately needed features in Emacs, and implementing them isn't going to be any easier after rebasing the runtime. No, being able to write code in JavaScript or Scheme isn't going to make things easier. It'll make things harder due to language fragmentation and impedance mismatches between the various languages.
- davexunit 13y agoThe idea isn't to write Emacs extensions in Scheme instead of Elisp, but to give Elisp a much more powerful environment in which to run. The Guile VM brings features such as delimited continuations, threading, and a C FFI that Emacs could benefit greatly from.