Ignas Mikalajunas writes:
>   Nice thingie, sad that it doesn't really work with CFFI.
> FFI::FOREIGN-CALL-OUT just barfs something about foreign pointers
> comming from a previous lisp session. Can really advanced FFI stuff
> (callbacks, multiple libraries loaded when compiling etc.) be saved in
> memory image at all?

I can confirm that the CFFI/CLISP combo doesn't play well with saving
cores. The main problem is that we're not reloading the shared
libraries. You can work around that by calling cffi:load-foreign-library
on whatever libraries you are using with CFFI after you load the
image.

Callbacks won't work as well and I don't have any quick work-arounds for
you. Adding an ignore-errors to %defcallback in cffi-clisp.lisp where
the code is freeing the previous foreign function and redefining the
callbacks after loading the saved core should work.

I'll bug our CLISP expert about this. :-)

-- 
Luís Oliveira
luismbo (@) gmail (.) com
Equipa Portuguesa do Translation Project
http://www.iro.umontreal.ca/translation/registry.cgi?team=pt

_______________________________________________
Gardeners mailing list
[email protected]
http://www.lispniks.com/mailman/listinfo/gardeners

Reply via email to