On Fri, May 8, 2009 at 7:31 PM, Peter Tsenter <
[hidden email]> wrote:
>> I guess it's not high on the priority list.
>
> That's not true. The only reason I turned to abcl that this is the most
> (best) ANSI compliant implementation of Common Lisp running on JVM. And your
> implementation of JSR-223 is a big step in the right direction.
Well, thanks! (to Ville too :) However, don't be afraid, I wasn't
saying I would stop working on JSR-223; just that I'm focusing on
other things now, but from time to time I manage to work a bit on it
too. That's how I discovered the silly bug in compileScript - prin1
instead of princ! How n00b of me. The funny thing is that in theory I
have unit tests to check these things, gotta remember running them
before SVN commit!
> The next would be to make a message associated with a thrown exception (much)
> more informative.
Yes, that's one of the things I'd like to improve. Another important
one is that the debugger-hook that throws Java exceptions, instead of
dropping you in the interactive Lisp debugger, has still some issues -
it doesn't appear to work in all cases. I'd also like more Java
integration in general, I was thinking of offering an easy Lisp
interface to e.g. collections, URLs, streams... (I'm working on Swing
right now).
> I don't care about standalone application, but as a scripting language, abcl
> was the easiest to incorporate into my application. And I did try JavaCC and
> ANTLR.
Heh, I guess having a built-in parser, interpreter and compiler is quite nice :)
> Regarding the bug: I did what was necessary to make it work.
Ok, now my fix is on SVN, too. If you have other bug fixes,
improvements, or ideas please let me know. For example, one design
decision I'm not very sure about is the default package of code
executed under JSR-223 being abcl-script-user instead of cl-user.
abcl-script-user USEs cl, abcl-script and java, so it's probably nicer
to use, but has its issues too (mainly, you have to remember you are
not in cl-user).
> And one more thing: if you substituted a line
>
> ScriptEngine lispEngine = new
> ScriptEngineManager().getEngineByExtension("lisp");
>
> with the following three
>
> ScriptEngineManager scriptManager = new ScriptEngineManager();
> scriptManager.registerEngineExtension("lisp", new
> AbclScriptEngineFactory());
> ScriptEngine lispEngine =
> scriptManager.getEngineByExtension("lisp");
>
> (or similar) it would make your example self-contained.
Hmm, I thought my example was already self-contained, because of the
ServiceProvider machinery that should automatically register
ScriptEngineFactories looking at a file in META-INF, inside abcl.jar.
Doesn't this work for you? In any case, I should add a comment to the
example explaining this, and the manual registration of the factory,
just to be sure.
Bye,
Alessio
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled.
http://p.sf.net/sfu/kodak-com_______________________________________________
armedbear-j-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/armedbear-j-devel
