1.1 A simple example of how to interface a foreign function
1.1.2 Loading foreign code
Once an interface has been created, the object code defining those functions (and indeed any variables) must be made available to LispWorks.
In Unix, LispWorks defines the functionlink-load:read-foreign-modules that either load object files (usually suffixed with ".o") directly into the Lisp image, extract any required object files from the available archive libraries (usually suffixed with ".a"), or load in shared libraries (usually suffixed with ".so"). Theread-foreign-modules function takes a list of module names as its argument.