I saw some discussion in the archives about extending the library loading functionality. There's a couple of things I'd like that I didn't see, and this may be an oversight on my part...
1) CFFI keep track of which foreign modules it had loaded and allow you to iterate through them 2) Have CFFI allow you to unload a foriegn library by name, which should fail if it is not loaded, otherwise return true.
I'd find this handy both for debugging and for cleaning up while a program runs.
Justin Heyes-Jones justinhj@gmail.com writes:
- CFFI keep track of which foreign modules it had loaded and allow
you to iterate through them 2) Have CFFI allow you to unload a foriegn library by name, which should fail if it is not loaded, otherwise return true.
Most of the functionality is there already. We just need to keep track of what's loaded. And implement a higher-level abstraction on top of %unload-foreign-library. (eg: we'll probably want to unload whole libraries that were defined with DEFINE-FOREIGN-LIBRARY, frameworks, etc...).
-
Justin Heyes-Jones -
Luís Oliveira