On Sat, Dec 13, 2008 at 7:47 PM, Erik Huelsmann <ehuels@...> wrote:
> Hi Alessio,
> Sorry for my late reaction, I've been too busy with work-work and a
> bad case of the flew. I'm getting better though. Thanks for the update
> you posted below. It's exactly what we needed to know.
No need to be sorry, I too waited a lot before sending my mail! ;)
I hope you'll get well soon.
> On Thu, Dec 11, 2008 at 10:50 PM, Alessio Stalla
> <alessiostalla@...> wrote:
>> This is to inform everyone on the status of the Java Scripting API
>> (JSR-223) support for ABCL, lying in its own branch in the ABCL SVN
>> tree, on which I've been working on and off from a few months.
> First of all let me - too - thank you so much for the contributions!
>> Most of the (Java-side) JSR-223 API has been implemented, including
>> the optional parts. This includes integrating ABCL with the scripting
>> engine discovery mechanism, loading Lisp code from strings or
>> arbitrary streams, support for direct invocation of Lisp functions,
>> Java interface implementation in Lisp, compilation of Lisp "scripts".
>> These APIs have been lightly tested, but not thoroughly.
> That's no problem. Do you plan to use this new feature in any of your
> own developments in the (near) future? It would be great if you did!
> (No problem if you don't ofcourse..)
Yes, I have some plans for it: first, I'm going to give a talk about
Lisp and DSLs to a few Java developers, this January, and I'm going to
show off ABCL and the JSR-223 support :) this will involve the
development of a simple DSL using ABCL - I'm thinking to some sort of
declarative GUI definition language, now that JavaFX has all that
hype... depending on my free time and how the DSL turns out to be, I
might promote this example to a full-blown open source project... I
had already started something similar few years ago but I abandoned it
because I lacked the skills and the long-term interest in developing
Then, I have another, now "frozen", project, a sort of graphical
object browser for Java (in very early stage). I plan to add Lisp
scripting support via ABCL, and maybe rewrite its horrible GUI using
the aforementioned GUI language. But this is in the far-away future :D
>> Besides the Java side of things, ABCL itself has been modified. Most
>> of the changes are actually implementations of new functionality - I
>> tried as possible to preserve the preexisting code. The only
>> remarkable deviation is that LispObject.javaInstance() no longer
>> throws an exception, but rather returns the object itself.
> That sounds like a sensible change. The remaining change you describe
> all seem great; I need to grow some understanding about them though.
Of course, especially given that I don't know very much of ABCL's
internals so I'm not aware of all the consequences, or best practices,
> I do have a question, though: do you think we should separate the
> changes and the scripting api itself into 2 merges from the branch to
> the trunk? I'm asking because it sounds like other functionality -
> meaning anything but the scripting api - would benefit from the
> availability too.
Yes, it is possible and sensible to do it, but if you don't mind, I'd
like first to check that those changes actually don't need Java 6, so
to still allow ABCL to be built with Java 5 if you don't need the
> Well, thanks again! And, if and when you have time to come back to the
> project: you're always welcome!
Thanks to you for giving me the opportunity to work on this great
piece of software! And, I'll surely contribute to the project again as
soon as I have more free time!