On Fri, Apr 8, 2011 at 10:50 PM, meh. <meh@paranoici.org> wrote:
let's say the eval'd string is
(asdf:load-system :craftd) if any of the loaded files have a syntax
error my eval function doesn't know something went wrong.
Is there a way to know that?

This has also been dealt with in the mailing list.
Second, my application is threaded, there's a worker system where each worker
has a thread so LISP code can be executed in different threads.

That's fine if the threads are created by ECL, but if they are created by your C/C++ application then you have to register them with ECL. Search the mailing list if this is your case.
If I put the threading stuff in the eval function it segfaults on the
release, so I guess I have to run those two functions after a worker
has started and before a worker is killed, is this right? Is there an
easier way to achieve thread safety for LISP execution?

I do not really understand this paragraph very well.


Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)