[armedbear-devel] [PATCH] jcall(there are multiple matchingmethods)

Tobias C. Rittweiler tcr at freebits.de
Tue Dec 22 21:07:01 UTC 2009

Alan Ruttenberg writes:

> This would be incompatible with other common lisps, and make porting
> to other java enabled lisps in the future a pain. My gut says don't
> mess with the define reading behavior.

I can't follow that line of logic; which other java-enabled Lisps of the
future are you talking of?

Why should ABCL care for java-enabled Lisps of the future? It should
become the java-enabled Lisp of the future: i.e. ABCL should strive to
become a hallmark for java integration.


More information about the armedbear-devel mailing list