>Well, if I understood the comments in src/org/armedbear/lisp/java.lisp
>correctly, then there's a macro there to generate java-like classes
>which can be accessed from java. Maybe that would help?
Well, the Interpreter object on the java side creates them anyway, so I don't really see
any problem. Personally I don't (anymore :) wish to be able to load abcl code directly
as java, because the Interpreter allows calling lisp functions and accessing lisp variables
*without having to eval*. So if the problem is that you don't want to eval strings every
time in order to invoke lisp code, you don't have to - the Interpreter has existing
methods for this.
ABCL in general lacks javadoc documentation, but the interface of Interpreter is
not that hard to grasp, IMHO.