lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Oops. I have just finished a tool to read C header 
and generate the wrapper coder for Lua. It's in python.

----- Original Message ----- 
From: "mark gossage" <>
To: <>
Sent: Friday, November 17, 2006 1:02 PM
Subject: Announce - SWIG-1.3.30

> Hello list,
> Just to let you know on the status of SWIG.
> Mark 
> ----------------------------------------------------------
> *** ANNOUNCE: SWIG 1.3.30 (November 13, 2006) ***
> We're pleased to announce SWIG-1.3.30, the latest installment in the
> SWIG development effort. SWIG-1.3.30 includes a number of bug fixes
> and large number of enhancements throughout.
> What is SWIG?
> -------------
> SWIG is a software development tool that reads C/C++ header files and
> generates the wrapper code needed to make C and C++ code accessible
> from other languages including Perl, Python, Tcl, Ruby, PHP, Java,
> Scheme (Guile, MzScheme, CHICKEN), Ocaml, Lua, Pike, C#, Modula-3, and
> Common Lisp (CLISP, Allegro CL, CFFI, UFFI). SWIG can also export its parse
> tree in the form of XML and Lisp s-expressions. Major applications of
> SWIG include generation of scripting language extension modules, rapid
> prototyping, testing, and user interface development for large C/C++
> systems.
> Availability:
> -------------
> The release is available for download on Sourceforge at
> A Windows version should also be available at
> What's New?
> ===========
> SWIG-1.3.30 summary:
> - Python-2.5 support
> - New language module: R
> - Director support added for C#
> - Numerous director fixes and improvements
> - Improved mingw/msys support
> - Better constants support in Guile and chicken modules
> - Support for generating PHP5 class wrappers
> - Important Java premature garbage collection fix
> - Minor improvements/fixes in cffi, php, allegrocl, perl, chicken, lua,
> ruby,
> ocaml, python, java, c# and guile language modules
> - Many many other bug fixes
> Release numbers
> ---------------
> With SWIG-1.3, we are adopting an odd/even version numbering scheme for
> SWIG. Odd version numbers (1.3, 1.5, 1.7, etc...) are considered to
> be development releases. Even numbers (1.4,1.6,1.8) are stable
> releases. The current 1.3 effort is working to produce a stable 2.0
> release. A stable 2.0 release will not be made until it can
> accompanied by fully updated documentation. In the meantime, we will
> continue to make periodic 1.3.x releases.
> We need your help!
> ------------------
> Even if you are perfectly happy with SWIG-1.1, we can still use your
> feedback. First, we like to know about compilation problems and other
> issues concerning the building of SWIG. Second, if SWIG-1.3 is unable
> to compile your old interface files, we would like to get information
> about the features you are using. This information will help us find
> bugs in the SWIG-1.3 release, develop techniques for supporting
> backwards compatibility, and write documentation that addresses
> specific issues related to migrating from SWIG-1.1 to SWIG-1.3.
> We are also looking for volunteers who would like to work on various
> aspects of SWIG development. SWIG is an unfunded project that would
> not exist without volunteers. We are also looking for the developers
> of other SWIG language modules. If you have developed a SWIG module
> and would like to see it incorporated into the new release, please
> contact us to obtain SWIG-CVS access. We are also more than willing
> to help port your module from SWIG-1.1 to SWIG-1.3. Please send email
> to for further information.
> Please report problems with this release to the swig-dev mailing list,
> details at
> --- The SWIG Developers