From: Erik Huelsmann <ehuels@gm...> - 2008-08-04 09:18:55
On 11/11/07, Ville Voutilainen <ville.voutilainen@...> wrote:
> I *finally* got some time to test the following scenario:
> 1) invoke java code from lisp (as usual)
> 2) lisp code invokes java code
> 3) java code invoked in 2) throws an exception
> This is handled by abcl so that the java exception thrown in 3) raises
> a condition
> of type java-exception, which can be handled in lisp code with usual
> I decided I like this approach, because although it is not transparent, it means
> that abcl code is not that tied to java. If we would have only
> lisp->java integration,
If you're not afraid to code to the internals of ABCL (they're not
that fast moving), I have a function called "safeFuncall" which
catches any uncaught conditions and raises them as Java exceptions of
> we could not assume that there is a java code layer invoking the lisp code.
> Therefore it's reasonable to let the lisp code handle the condition, instead
> of letting the java exception travel through. As discussed before, it's further
> possible to map the condition to a ConditionThrowable at the java code
> that is run at step 1).
Exactly. Want to have the code? Or maybe I should suggest adding this
code to the LispObject implementation?