RE: embeddability

[Konovalov, V. \(Vadim\)** C. ** <vko...@al...>]

> > Why a separate thread?
> 
> the back_trace object has to be bound on the C stack above 
> all the lisp
> computations, so all lisp work has to be done inside run_clisp.
> starting a new clisp (loading image &c) for each evaluation is too
> expensive, so the users will start clisp in a separate thread 
> and ask it
> to do some work every now and then.
> 
> > Why no direct invocation of a Lisp function given by name?
> 
> the name will be passed to f and the function will be called.

my lisp foo is limited, but IMO embedding this way does nothing: CLISP
already can be embedded this way using sockets and separate threads, one
just needs to write small wrapper and all is done.

Much better is traditional way, where user have API lib (which refers to
either static or shared library), and link with it at his will.
At least embedding Perl or Tcl is this simple.

BR,
Vadim.