I passed a pathname to load-foreign-library and Clisp complained that it was not a string. Maybe I missed something. Anyway, if CLisp indeed has a limitation in re accepting a pathname for a library, maybe the CFFI wrapper could add that flexibility.