[Openmcl-devel] reloading/unloading shared libraries?
peter at javamonkey.com
Mon Feb 9 11:54:51 PST 2004
Gary Byers <gb at clozure.com> writes:
> I think that you can do what you want to do by:
> - using bundles instead of dylibs.
Am I doing that if I'm using the -bundle flag to gcc?
> - try to ensure that a bundle's loaded at most once.
> - when it's time to test a new version of a bundle, call
> CLOSE-SHARED-LIBRARY to cause all "external entry points" associated
> with the library to become unresolved. Loading a new version of the
> library should cause the "external entry points" of those foreign
> symbols to associate themselves with the new library instance.
> This should work for things like (external "_foo") and
> (external-call "_foo" ...), which are sort of designed around the
> notion that a foreign symbol's address can change.
Cool. That's exactly what I'm interested in--just developing without
having to restart Lisp every time I make a change to my C code.
Peter Seibel peter at javamonkey.com
Lisp is the red pill. -- John Fraser, comp.lang.lisp
More information about the Openmcl-devel