From: Goffioul M. <gof...@im...> - 2004-08-18 09:46:15
|
Hi, =20 First of all, thanks to anybody who helped me hacking CLISP to get it = embeddable (especially Sam). I finally got a usable version of embedded CLISP, and = used it to build a MATLAB->LISP bridge with success. I cannot provide any patch for = the moment, as the CVS server seems to be down still. But I give below a brief = summary of the changes I made to the CLISP code: =20 1) makemake.in: added rules to build a shared library; only GNU compiler = is supported, and lisp.run is not linked against that shared lib (still a static = executable) =20 2) spvw.d: extracted needed code from "main" and "quit", created "clisp_init(uintL memneed, char *memfile)" and "clisp_finish()"; longjmp = is hanlded locally in clisp_init to allow safe termination if a problem occurs during = initialization =20 3) eval.d: added a global error handler that is used in = "invoke_handlers" if no other handler is found; this global error handler can be defined using API and must be = a nonreturning function =20 4) genclisp.d: uncommented some useful definitions for complex, ratio, = array...; exported additional functions like "eval", "apply" =20 5) array.d: added "array_data" global function to access to storage = vector of a given array =20 This is certainly not perfect, neither complete, but it's at least a = good start and it seems to suit my current needs. =20 Bye. Michael. =20 |