From: Kevin Layer
Subject: Announce: SWIG / Allegro CL integration
Date: 
Message-ID: <mklljgnt49.fsf@*n*o*s*p*a*m*franz.com>
We have recently committed to sourceforge.net our changes to integrate
SWIG (a tool for automatically generating interfaces to C/C++
libraries, see www.swig.org) and Allegro CL.  At this moment, the
changes are only available in the CVS repository, or on our FTP site.

For those who have never heard of SWIG, it's quite popular in the
Python and Perl communities.  There are an amazing number of SWIG
interface files, as they are called.

You can read about it here:

  http://www.franz.com/support/tech_corner/swig042804.lhtml

If you have comments on the Allegro CL version, send them to
·······@franz.com.

Kevin Layer
Franz

From: Kenny Tilton
Subject: Re: Announce: SWIG / Allegro CL integration
Date: 
Message-ID: <01Ssc.92767$Nn4.20303316@twister.nyc.rr.com>
Kevin Layer wrote:
> We have recently committed to sourceforge.net our changes to integrate
> SWIG (a tool for automatically generating interfaces to C/C++
> libraries, see www.swig.org) and Allegro CL.  At this moment, the
> changes are only available in the CVS repository, or on our FTP site.
> 
> For those who have never heard of SWIG, it's quite popular in the
> Python and Perl communities.  There are an amazing number of SWIG
> interface files, as they are called.

Did someone say, "More libraries!"?

So anything already swigged is now available to CL? Is this contrib as 
awesome as it seems, or am I missing something? I'll go RTFLink now.

Last one to do an UFFI port is a rotten egg.

Thx for the contrib,

kenny


-- 
Home? http://tilton-technology.com
Cells? http://www.common-lisp.net/project/cells/
Cello? http://www.common-lisp.net/project/cello/
Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film
Your Project Here! http://alu.cliki.net/Industry%20Application
From: rif
Subject: Re: Announce: SWIG / Allegro CL integration
Date: 
Message-ID: <wj0zn7vc45i.fsf@five-percent-nation.mit.edu>
While this is clearly a step in the right direction, I'm unclear what
proportion of libraries will be supported given the current
limitations.  I recently wrapped the R library using UFFI, and it
extensively used many of the features not currently supported by
SWIG/ACL --- unions, bitfields, and functions that take string
arguments.  Still, as a first step, it seems great.

rif

ps.  If I'm not mistaken, there's already "experimental" support for
UFFI in the SWIG CVS tree.  I've never tried to use it, so I don't
know what state it's in.
From: Svein Ove Aas
Subject: Re: Announce: SWIG / Allegro CL integration
Date: 
Message-ID: <g_Xsc.3994$eH3.71483@news4.e.nsc.no>
rif wrote:

> 
> While this is clearly a step in the right direction, I'm unclear what
> proportion of libraries will be supported given the current
> limitations.  I recently wrapped the R library using UFFI, and it
> extensively used many of the features not currently supported by
> SWIG/ACL --- unions, bitfields, and functions that take string
> arguments.  Still, as a first step, it seems great.
> 
> rif
> 
> ps.  If I'm not mistaken, there's already "experimental" support for
> UFFI in the SWIG CVS tree.  I've never tried to use it, so I don't
> know what state it's in.
>
Well, this certainly sounds useful to me.
I don't have time for it right now, but I'll see what I can do with it in
a few weeks.