2008/9/4 Andy Wingo <[EMAIL PROTECTED]>:
>
> I think it makes a *lot* of sense to compile elisp to the VM. I don't
> plan on doing so myself, but if the VM gets good enough, it could be
> enhanced with the instructions that elisp needs, if any, and it would be
> possible to run emacs lisp code, and possibly even emacs itself, on
> guile.
That sounds good for elisp code. For "even emacs itself", the
obstacle is implementing the vast crowd of emacs primitives...
> I don't know where the boundary lies regarding C primitives, though. I
> think we'll eventually want to make VM-implemented functions as fast or
> faster than the C ones, through a tracing JIT or something. So you could
> make elisp reference different C primitives, or implement its primitives
> in elisp (or scheme, or whatever), or make our C primitives do both.
Currently, in lang/elisp/*, a handful of emacs primitives are
implemented in Scheme. I suspect the only sane long term solution
would involve reuse of the Emacs code - which then would make the
lang/elisp/* experiment converge with Ken Raeburn's experiment.
Regards,
Neil
