Erann Gat <gNOSPAMat@flownet.com> wrote:
+---------------
|  Duane Rettig <duane@franz.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:

  Newsgroups: comp.lang.lisp
  From: Eric Marsden <emarsden@laas.fr>
  Subject: Re: does CMUCL garbage-collect object code?
  Date: Wed, 31 Mar 2004 11:48:38 +0200
  Message-ID: <wzin05x9wjt.fsf@melbourne.laas.fr>

or:

  <http://www.google.com/groups?as_umsgid=wzin05x9wjt.fsf%40melbourne.laas.fr>

The function RELOAD-SHARED-LIBRARIES, which he cheerfully admits is
CMUCL-specific and nowhere near "supported".


-Rob

-----
Rob Warnock			<rpw3@rpw3.org>
627 26th Avenue			<URL:http://rpw3.org/>
San Mateo, CA 94403		(650)572-2607