Raymond Toy writes:
>>>>> "Jerry" == Jerry James
<james(a)xemacs.org> writes:
Jerry> Somewhat ironically, I actually considered this preprocessor a step
Jerry> towards an Elisp-to-C translator, using the source to be preprocessed as
Jerry> the target of that translator. I'll rethink that, too.
What's wrong with an Elisp-to-C translator? That's how GCL and
friends compile their Lisp code. (Of course, I'd rather that elisp
were closer to common lisp with real lexical closures by default.)
Several years ago there was a project over at one of the German
universities to write a Common Lisp to C Compiler (CLiCC). The last
version (v0.6.5) claimed that it conformed to the Common Lisp
specification in CLtL1 plus CLOS. The web site for the compiler is
still active:
http://www.informatik.uni-kiel.de/~wg/clicc.html
A couple of years ago I used it to compile several small stand alone
apps. I think that if someone were to pick up CLiCC and finish it (bring
it up to ANSI Common Lisp compliance), it would probably make a good
mechanism for developing something like XEmacs almost completely in
Common Lisp. I intend to do something like this eventually.
I would have already started, but all the inline comments are in
German and I don't have the time to learn German just so that I can
read the comments.
Craig