Version 1 (modified by 11 years ago) (diff) | ,
---|
Make LispObject? a Java interface, as God and Gosling intended.
LispObject as interface thing
makes a great summer project. Especially if you make it a semi-pluggable object with the contemporary architecture, write benchmarks, and write up the results.
A don't think that a
unitary LispObject interface is a good idea: I'd rathe see LispObject be union of interfaces (HasPrintableForm?, HasNumericTower?, etc.) And provide a polished set of AbstractLispObjects? (AbstractJavaLispObject?, etc.) to work with.
Then factor the existing code into a Java5/6 implementation of LispObject?. Then, provide an implementation of LispObject? that will work on .NET and/or Dalvik.