On Thu, 14 Oct 2004, John Morrison wrote:
> given that the whole point of the exercise is to load a shared
> library, at binding-build-time I should require not only the output of
> gccxml corresponding to the library, but the library itself. Then, I
> could check whether the symbol exists before emitting its binding.
Sounds sane to me.
Now that you mention it, I'd suggest that you use dlopen RTLD_LOCAL &
dlsym to discover if the symbol exist (as opposed to hooking into SBCL
internals): this way you can be sure that the symbol really is in the
library and not in some other library currently loaded into SBCL, and also
avoid future breakage due to internal interfaces changing.
-- Nikodemus Schemer: "Buddha is small, clean, and serious."
Lispnik: "Buddha is big, has hairy armpits, and laughs."