[Openmcl-devel] Shared library bug?

[Andrew P. Lentvorski, Jr.]

Is this a bug?

Welcome to OpenMCL Version (Beta: Darwin) 0.14.2-040506!
? (open-shared-library "/Users/devel/lib/libgdk-x11-2.0.dylib")
#<SHLIB /Users/devel/lib/libgdk-x11-2.0.dylib #x638EF46>
? (external "_gdk_draw_point")
#<EXTERNAL-ENTRY-POINT "_gdk_draw_point" (#x006BC838) 
/Users/devel/lib/libgdk-x11-2.0.dylib #x638EE1E>
? (external "missingfuncbleahfoo")
#<EXTERNAL-ENTRY-POINT "missingfuncbleahfoo" {unresolved}  #x638EBCE>

The missing function just claims to be unresolved rather than 
completely missing altogether.  Is this expected?

Also, is there a way to get a list of the available functions 
associated with a loaded shared library from inside OpenMCL?  What I am 
trying to do is take the *.defs files from PyGtk (which are written in 
Scheme and match the Gtk interface) and map them into OpenMCL.  It 
would be useful to know which functions actually exist in the library 
to avoid mapping missing functionality.

-a