This is the mail archive of the
libffi-discuss@sources.redhat.com
mailing list for the libffi project.
RE: minimal closure usage
- From: "Sam Liddicott" <sam dot liddicott at ananova dot com>
- To: "Anthony Green" <green at redhat dot com>, "Sam Liddicott" <sam dot liddicott at ananova dot com>
- Cc: <libffi-discuss at sources dot redhat dot com>
- Date: Tue, 30 Apr 2002 15:34:05 +0100
- Subject: RE: minimal closure usage
> -----Original Message-----
> From: Anthony Green [mailto:green@redhat.com]
> Sent: 30 April 2002 15:19
> To: Sam Liddicott
> Cc: libffi-discuss@sources.redhat.com
> Subject: Re: minimal closure usage
>
> > (BTW: Is there an
> array/structure/function/full-set-of-rules to convert
> > between "int" and "ffi_type_sint" etc? SWIG would need to
> refer to this as
> > it generates the sample code below)
>
> No, not really. I think, however, that "int" always ==
> "ffi_type_sint".
Perhaps I could contribute an (ugh) set of macros which taking standard
types expand out to ffi_type stuff?
I think it's pretty much essential if swig is to be able to use it without
becoming too platform specific itself or being tied too strongly to the
state of libffi.
> It's just the ffi_type_sint32, etc, which
> are platform
> specific.
Are they?
Why ffi_type_sint and not ffi_type_int ?
Sam