Erann Gat <gNOSPAMat@flownet.com> wrote:
| Duane Rettig <email@example.com> wrote:
| > Be sure to dlclose() the handle first, to release and gc the old
| > inode and so that the dlopen will grab the new file.
| That is probably the key. But this is problematic because now you have
| to keep track for every function that you load which file it came from.
| When you redefine a function you have to close its corresponding library,
| and then make sure that *all* of the functions defined in that library get
| restored in the new version. It's a titanic pain in the barumpus.
Somebody posted some code here just recently to do *exactly* that...
Now where was it...? *AHA!!* Here it is:
From: Eric Marsden <firstname.lastname@example.org>
Subject: Re: does CMUCL garbage-collect object code?
Date: Wed, 31 Mar 2004 11:48:38 +0200
The function RELOAD-SHARED-LIBRARIES, which he cheerfully admits is
CMUCL-specific and nowhere near "supported".
Rob Warnock <email@example.com>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607