This is the mail archive of the
libffi-discuss@sources.redhat.com
mailing list for the libffi project.
RE: SWIG and callback wrappers
- 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:37:11 +0100
- Subject: RE: SWIG and callback wrappers
> -----Original Message-----
> From: Anthony Green [mailto:green@redhat.com]
> Sent: 30 April 2002 15:12
> To: Sam Liddicott
> Cc: libffi-discuss@sources.redhat.com
> Subject: RE: SWIG and callback wrappers
>
>
> On Tue, 2002-04-30 at 01:43, Sam Liddicott wrote:
> > Do any normal-releases of gcc contain a libffi? Or will it
> just be a future
> > release?
>
> I think it started with GCC 3. However, I'm pretty sure it's just
> _used_ in libgcj, and not installed for others to use.
>
> I've been putting off making a new libffi standalone release
> for a very
> long time. I'll try (again) in May, but for now I suggest just jury
> rigging a solution with the GCC version.
Well the swig release date is June. When libffi is not available we'll have
a load of identical callback functions each with some individual static
storage. We'll allocate these functions out as needed till they are all
used up. So while libffi provides the no-limits callback handling we'll not
be stuck if a release is delayed.
Swig users will not be able to jury-rig gcc but will be able to install
libffi if required.
Do you suppose that when (or earlier) your enhancements are built back into
gcc that it will be available as part of gcc and not just secretly within
gcc.
Sam