On Fri, Jan 8, 2010 at 5:39 PM, Alessio Stalla alessiostalla@gmail.com wrote:
My main objection against jsint is that it requires an additional jar on the classpath, of which it uses just a few classes. But read on.
Just to reply to this point.
I wouldn't distribute it that way. I'd either extract just the class files necessary and have the build include them in abcl.jar, or just get the relevant source files, put them in the ABCL source tree, and adapt them as necessary.
Certainly now that we have the ability to load asds directly from a jar my plan is to distribute my code as a single jar in which I've included abcl, the contents of all the jars that my tool depends on, and all the compiled lisp code. Goodbye class path.
Any yes, of course I can continue to use jsint myself, however as I found it quite useful I was hoping to spread the goodness around more widely :)
Cheers, Alan