Re: [j-devel] Different behavior of Function.invoke(...) between interpreted and compiled functions?

[Alessio S. <ale...@gm...>]

On Wed, May 13, 2009 at 11:55 AM, XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX wrote:

> You could even do it differently:
>
>  LispThread.currentThread().execute(Symbol.APPLY, ...);
>
> Which makes it appear in the stack trace when you use the debugger.
> Ofcourse, if you already have a local 'thread' variable, you could use
> that, instead of "LispThread.currentThread()".
>
> I think that executing the symbol through the thread is the best Lisp
> way: it takes the function slot from the symbol, meaning that APPLY
> can be redefined by assigning the function slot a new value. At the
> same time, I think it approaches a 'nice' Java-like approach.

Ok, thanks, good advice, I'll do it like that.

Ale