On Dec 16, 2004, at 3:10 AM, Eric Marsden wrote: > > LOAD-FOREIGN does not search the standard library paths. The reason > for this behaviour is that if the file exists but is not a shared > library (for instance a normal .o file), CMUCL will ask the linker > to load it. I will try to clarify the documentation in this respect. > > Perhaps LOAD-FOREIGN would be more useful if it worked as you > expect. I fear that changing it would make the diagnostics available > on error less useful than they currently are, since dlerror() does > not work very well in my experience (on Linux).
I grabbed a copy of the source, and saw that system::load-object-file would do what I wanted. That was confirmed by another kind person on this list. Perhaps load-object-file could be exported from the system package, as an alternative for users who want the searching behavior? Regards, Craig Ludington
