Re: [Sbcl-help] How to cope with undefined foreign symbol during macro expansion?

[Nikodemus S. <tsi...@cc...>]

On Tue, 12 Oct 2004, John Morrison wrote:

> I think I have handled the "obvious" cases of "artificial" functions
> (e.g., copy constructors) defined yet not always generated by GCC, and
> I prevent them from appearing in the bindings.
>
> However, if system header files are included in any of the source
> (say, <stdio.h>, <typeinfo>), they may declare system functions that
> will not be in my shared library.  I am not sure if it's computable to
> identify them and prevent their inclusion in the auto-generated lisp
> bindings.  I have to think about this.
>
> Anyway, that's why I wanted to ignore any errors like that.

Aha, gotcha. So presumably signalling UNKNOWN-FOREIGN-FUNCTION-ERROR or
some-such would solve this for you -- as then you'd be able to handle 
those?

Cheers,

  -- Nikodemus              Schemer: "Buddha is small, clean, and serious."
                   Lispnik: "Buddha is big, has hairy armpits, and laughs."