cees-bart said:
> anyway, the problem is solved, and indeed, the call to ld which > load-foreign > prevents > its use on shared objects, and yes you can solve this by calling > system::load-object-file. This is not true. If ext:load-foreign doesn't work for you, that is a bug, and should be reported in the usual manner (which includes a little more information than a single question, FWIW). Otherwise ext:load-foreign should work for loading shared objects on all supported platforms. There are disadvantages to using ext:load-foreign for shared objects, and there is ongoing discussion on changing ext:load-foreign to directly call system::load-object-file for shared objects, but those issues shouldn't prevent simple uses of ext:load-foreign for shared objects. > i do think this should be in the cmucl section on aliens though. if it was > in the reference manual, > i wouldn't be tempted to ask the stupid question in the first place. the > xported symbols do not > contain load-object-file. Which is of course the reason why system::load-object-file isn't documented in the reference manual. We will however gladly accept patches to the cmucl code base (_and_ the manual, if the code changes the documented interfaces in material ways), that will improve the foreign object loading facilities (simply exporting and documenting load-object-file is not enough!). Or feel free to contract any of the available developers to develop said patches. Regs, Pierre. -- Pierre R. Mai <[EMAIL PROTECTED]> http://www.pmsf.de/pmai/ The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents. -- Nathaniel Borenstein
