4 ms·
It seems dynamic scoping is not really an issue for Guile to host Emacs Lisp. See the paragraph from the README[1] of the current implementation: flet and
by p4bl0 15y ago
It seems dynamic scoping is not really an issue for Guile to host Emacs Lisp.
See the paragraph from the README[1] of the current implementation:
flet and flet*:
---------------
These constructs behave exactly like let and let*, except that they bind
the function slots rather than the value slots, and so make dynamic scoping
available for functions, too.
To me this sounds like the dynamic scoping issue has already been solved.
[1] http://git.savannah.gnu.org/gitweb/?p=guile.git;a=blob;f=module/language/elisp/README;hb=HEAD http://git.savannah.gnu.org/gitweb/?p=guile.git;a=blob;f=mod...
- gruseom 15y agoNo, that's about writing an Elisp compiler in Guile. Yoklov was talking whether Guile itself is as suitable an extension langauge as Elisp.
- p4bl0 15y agoRight but what if this compiler could JIT elisp to the Guile VM? It would use Guile but still be elisp compatible. Am I wrong?
- gruseom 15y agoAs far as I know (but I'm not the person to ask), their goal is to swap a new (Guile-based) Elisp implementation into Emacs that is 100% compatible with existing programs. That seems like a sine qua non if their plan is to have any chance.