| 4 | | 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. |
| | 4 | Make LispObject a Java interface, as God and Gosling intended. Over the history of ABCL, it has been often mooted whether LispObject should be defined by the Java interface abstraction, allowing different implementations, or if was better just to throw everything into a root object ('LispObject') that everything has to inherit from. For the JVMs available at the turn of the 21st century, having large static, kitchen-sink objects in Java code was commonly received as wisdom. Whether this is true a decade later can be verified in a summer of the Bear. |
| | 5 | |
| | 6 | 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. |
