4 ms·
I don't know LISP well enough to ponder how portable all the existing elisp code base would be portable to CL. Imho this could be the deciding factor between a
by babarock 15y ago
I don't know LISP well enough to ponder how portable all the existing elisp code base would be portable to CL. Imho this could be the deciding factor between a permanent shift for emacs or a mere fork.
- jrockway 15y agoIt's not portable. A compiler would have to be written, and it would not produce human-editable output. Emacs Lisp will be around forever, but that doesn't mean that it needs to run slowly or be the only language with which to extend Emacs. (This is a Python 2 / Python 3 type of situation. Some programs can be automatically translated, but nobody really wants to maintain the result. A proper Python 3 port is the correct solution, using the automatic translation as the basis.)
- lispm 15y agoThere have been attempts to run Elisp in Common Lisp. Generally it would not be that difficult to have both Elisp and Common Lisp in one Lisp. Whether it makes sense to go that route and have enough community support is another question.