From: Robert B. <rob...@gm...> - 2005-09-15 02:07:14
|
Today, I used SBCL to compile and load matlisp. Matlisp requires a shared library that's loaded as follows: (sb-alien:load-shared-object "matlisp:lib;libmatlisp.so") After Matlisp is loaded up, one dumps SBCL's state with a function that calls SB-EXT:SAVE-LISP-AND-DIE. Before dumping SBCL, however, I changed th= e logical pathname translation for MATLISP, hopeful that SBCL would, upon restart, load the Matlisp library from the new location. Unfortunately for me, it looks like SBCL caches the Unix file name associated with the shared object, not the logical pathname, so that when SBCL is run again, it tries to load the library from the exact same spot, even though MATLISP now point= s elsewhere. Does this sound like the Right Thing or should SBCL cache the argument of LOAD-SHARED-LIBRARY instead of the result of calling SB-INT:UNIX-PATHNAME o= n the argument? bob |