Re: CLISP support ?

As you propose UFFI support for CLISP to whomever takes up the task, I'd
also like to add a feature request or two so that CL-SDL can take
advantage of the CLISP FFI as well, in ways that go beyond current UFFI.

CL-SDL uses, and UFFI supports:

foreign functions, types, structs, unions, pointers, heap allocation and
deallocation, cstrings, and arrays.

UFFI does not currently support:

foreign funcall of function pointers (or function pointer types, I
think), out and in-out function arguments, casting, and callbacks.

[in descending order of importance to CL-SDL, in particular the first
one I am currently trying to implement portably]

Also worth thinking about is an interface that is flexible enough to
support run-time type and slot determination, but also be capable of
compile-time optimization where possible.

CL-SDL currently assumes only compile-time types and slots may be
available, but I would like to see that go away eventually.

I'm hoping that I can collect all these features and formulate them
better, sometime, possibly to be the basis of UFFI2.

-- 
; Matthew Danish <[email protected]>
; OpenPGP public key: C24B6010 on keyring.debian.org
; Signed or encrypted mail welcome.
; "There is no dark side of the moon really; matter of fact, it's all dark."