Changes between Version 10 and Version 11 of GSOC/ProjectProposals


Ignore:
Timestamp:
02/18/11 09:13:08 (11 years ago)
Author:
Mark Evenson
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSOC/ProjectProposals

    v10 v11  
    1717== [wiki:GSoC2011/LispObject-as-java-interface Make LispObject a Java interface] ==
    1818
    19 Make LispObject a Java interface, as God and Gosling intended.  LispObject should be a union of superinterfaces (like HasPrintableRepresentation, HasNumericTower) for which the current code is abstracted into common implementations.  Patches exist for some of from previous version.  This project would first study that code, decide whether to bring those changes forward to abcl trunk or start from scratch, provide the implementation as a pluggable alternative to  the current one, benchmark the differences, and write up the result in a short paper. 
     19Make LispObject a Java interface, as God and Gosling intended.  LispObject should be a union of superinterfaces (like !wiki:HasPrintableRepresentation, !wiki:HasNumericTower) for which the current code is abstracted into common implementations.  Patches exist for some of from previous version.  This project would first study that code, decide whether to bring those changes forward to abcl trunk or start from scratch, provide the implementation as a pluggable alternative to  the current one, benchmark the differences, and write up the result in a short paper. 
    2020
    2121Just doing the above makes a nice summer project, but there is much more that could be done regarding portability , such as providing an implementation of LispObject that will work on .NET 9via IKBM) or Dalvik.  Or Java7 with InvokeDynamic. Or ...?
     
    2727== Improve Java interoperability ==
    2828
    29 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. 
     29Looking at the best ideas from ABCL's JAVA package and [http://lsw2.googlecode.com/svn/trunk/jss/invoke.lisp 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. 
    3030
    3131== Implement a better debugging facility ==