Just ensure your functions have prototypes as required. I mentioned libffi only as part of the general discussion of calling conventions, because it comes up when writing interfaces to foreign languages. Even when Chicken is configured to use libffi internally, it doesn't apply to foreign calls. (No pun intended.) That's what lazy-ffi does, but don't go down that path either :)
On 8/28/06, Shawn Rutledge <[EMAIL PROTECTED]> wrote:
You are saying just use libffi and it's all much better?
On 8/28/06, Zbigniew <[EMAIL PROTECTED]> wrote: > libffi exists in great part to handle hairy calling conventions. I > found this out the hard way while writing the Objective C interface.
_______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
