Re: Re: validity of foreign functions across saved image s

Hoehle, Joerg-Cyril wrote:
> What happens if Allegro cannot find that library? CLISP's FFI on
> Amiga would error out, which is IMHO not acceptable.

I suspect the same will happen on Allegro.

> And ff:load-foreign-library makes all old function pointers valid
> again?

Apparently so.

> Are they scanning the shared object for names?  Or do they remember
> all functions from this library and revalidate, e.g. maintain a
> table of functions objects and dlsym() each in turn, after reopening
> the library?  I can't believe so, since a symbol found via dlsym()
> need not necessarily be in the library opened via dlopen() -
> depending on flags.

You could try asking at info-OnabZ2Gd1GpfmgfxC/sS/[email protected]

> E.g., I believe Allegro UFFI users don't supply :module most of the
> time: I suspect Allegro to look for the symbol in any currently opened
> library.

The only platform that needs :module is Lispworks.

> It's not finished nor released. I guess I'm too much of a "better is
> worse" guy. I want to have some idea about how to do FF across images
> before I throw in something which could not cope. I've yet to live
> more with increments.

I understand, best wishes with that.
> 
-- 
       Kevin Rosenberg        |  .''`.  ** Debian GNU/Linux **
  http://b9.com/debian.html   | : :' :      The  universal
  GPG signed and encrypted    | `. `'      Operating System
     messages accepted.       |   `-    http://www.debian.org/