3 ms·
This is the same strategy that Clojure is now using, which is why it's the only LISP that has any chance of going mainstream.
by sutro 17y ago
This is the same strategy that Clojure is now using, which is why it's the only LISP that has any chance of going mainstream.
- kqr2 17y agoI don't think Clojure uses the same "trojan horse" strategy, i.e. it isn't a superset of the Java language with Lisp extensions. It does use the Java virtual machine, however, which allows it to use existing java libraries.
- dkarl 17y agoImplementing Java interfaces and subclassing Java classes does allow Clojure programmers to introduce Clojure into a Java organization without forcing the Java programmers to accommodate them in any special way. (That is, as long as Clojure code can be deployed easily as jars, and as long as Clojure doesn't create any special classloader problems because of its runtime system. Those are problems that bit me hard when I used Jython code in the Eclipse plugin framework, and I imagine any dynamic language might accidentally create classloader problems unless it was specifically designed to avoid them.)