Re: the foreign c-string type: what animal is that?

> Precisely, I've always said that CLISP's FFI has already 90% or what is
> needed. You're pushing me hard: stack-allocation, malloc+free + dynamic
> functions + API design all at the same time... -- six years after the
> FFI (and creation of the ffcall package which perl uses to do dynamic
> calls -- a shame).

Wow, that is a lot of work! John Desoi says the MCL port is about done.
I'm not in a rush for you to do those things in CLISP, but won't
that be great if CLISP can support UFFI, too? That'd be the 5 major
CL platforms.

Best wishes,

Kevin