Changes between Version 2 and Version 3 of JavaFfi/RuntimeClass


Ignore:
Timestamp:
07/05/12 21:07:18 (8 years ago)
Author:
Alessiostalla
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • JavaFfi/RuntimeClass

    v2 v3  
    1111== History ==
    1212
    13 == Status ==
     13ABCL used to have a form of runtime-class functionality in its early days. It was implemented using the popular ASM library. At one point, though, it was disabled in order to eliminate the need for external dependencies. It stayed disabled for quite a long time - enough for getting affected by bit rot with a high probability.
    1414
    15 == Missing pieces and design considerations ==
     15Between late 2011 and early 2012, part of the functionality was resurrected by Alessio Stalla, this time completely in Lisp with no external dependencies. This was made possible by ABCL's class file writer, an internal library coded some time earlier by Erik Huelsmann to better separate concerns in the compiler. The class file writer was slightly extended in order to make it generate Java 1.5 annotation metadata.
     16
     17The API has been inspired by the original, but has been changed in some places.
     18
     19== The java:define-java-class macro ==
     20
     21'''This functionality is not yet implemented.''' The define-java-class macro is the high-level entry point to the runtime-class functionality. It takes a specification of a Java class and expands into code for generating such a class at runtime. If the macro is expanded as part of file compilation, it ('''optionally?''') generates the class at compile-time, dumps it to a file, and expands into code for loading the class from that file.