Changes between Version 5 and Version 6 of GSOC/ProjectProposals

Timestamp:

02/17/11 06:30:24 (11 years ago)

Author:

Mark Evenson

Comment:

--

GSOC/ProjectProposals

@@ -15 +15 @@
 Difficulty of this project may be that generic functions are based on the FUNCALLABLE-INSTANCE class, for which some investigating may be required to determine if its supports is up to the task of implementing generic functions with non-standard metaclasses.
 
-== Make LispObject a java interface ==
+== Make LispObject a Java interface ==
 
-Make LispObject a Java interface, as God and Gosling intended.  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 Davlik.
+Make LispObject a Java interface, as God and Gosling intended.  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.
 
-== Port to Davlik == 
+== Port to Dalvik == 
 
-First get the ABCL interpreter booted on Davlik.  Then, modify our complier to emit either JVM or Davlik bytecode.
+First get the ABCL interpreter booted on Dalvik.  Then, modify our complier to emit Dalvik bytecode.
+
+== Improve Java interoperability ==
+
+Looking at the best ideas from ABCL's JAVA package and Alan Ruttenberg's JSS package while studying the best patterns from Clojure, design and implement an interface possibly using macros, auto-magic PACKAGE import, and other standard language extension features that allow Java developers to easily use ABCL but has solid Common Lisp foundations.  
+
+== Implement a better debugging facility == 
+
+ABCL could use a facility to inspect the current Lisp stack frame as well as maintaining better correspondence between compiled and source code.  The ultimate goal would be the ability to single step through Lisp programs.