Hi Clinton, On Tue 31 Mar 2009 13:28, Clinton Ebadi <clin...@unknownlamer.org> writes:
> This is an excellent plan! Agreed! > There is already a working elisp->scheme translator for the interpeter > in lang/elisp. Yes, that would be a great starting point. > replacing the @fop and @bind operators in the interpeter with a bit of > GHIL implementing the same behavior. We can add ops to the VM if needed. > - Remove handling of NIL in Scheme. I used to think as you do, but Neil convinced me otherwise. For me, %nil can stay. > - Reimplement the basic elisp list operators in elisp/ghil rather than > using the existing Scheme implementations This could be interesting but doesn't seem necessary > - [Potentially] Remove value/function slots from Guile's symbol type > and implement the Lisp-2ness of elisp in another way Dunno. > - [Assuming the above is done; if not ((fref SYMBOL) ...) works > already] Implement a convenient way to call elisp functions from > Scheme. Something like (funcall SYMBOL ...) As Neil mentions, this seems possible already -- though not with VM code. Cheers, Andy -- http://wingolog.org/