PageRenderTime 12ms CodeModel.GetById 10ms app.highlight 1ms RepoModel.GetById 0ms app.codeStats 0ms

/tags/rel-1-3-24/SWIG/ANNOUNCE

#
#! | 65 lines | 51 code | 14 blank | 0 comment | 0 complexity | c024e84494ea5b7100a32c7d12254a17 MD5 | raw file
Possible License(s): LGPL-2.1, Cube, GPL-3.0, 0BSD, GPL-2.0
 1*** ANNOUNCE: SWIG 1.3.24 ***
 2
 3http://www.swig.org
 4
 5December 14, 2004
 6
 7We're pleased to announce SWIG-1.3.24, the latest installment in the
 8SWIG development effort.  SWIG-1.3.24 includes a number of bug fixes
 9and large number of enhancements throughout.
10
11What is SWIG?
12-------------
13SWIG is a software development tool that reads C/C++ header files and
14generates the wrapper code needed to make C and C++ code accessible
15from other languages including Perl, Python, Tcl, Ruby, PHP, Java,
16Guile, MzScheme, Ocaml, Chicken Scheme, C#, and Allegro Common Lisp.  
17Major applications of SWIG include generation of scripting language
18extension modules, rapid prototyping, testing, and user interface
19development for large C/C++ systems.
20
21Availability:
22-------------
23The release is available for download on Sourceforge at
24
25     http://prdownloads.sourceforge.net/swig/swig-1.3.24.tar.gz
26
27Within the next day, a Windows version will also be made available at
28
29     http://prdownloads.sourceforge.net/swig/swigwin-1.3.24.zip
30
31Release numbers
32---------------
33With SWIG-1.3, we are adopting an odd/even version numbering scheme for
34SWIG.  Odd version numbers (1.3, 1.5, 1.7, etc...) are considered to
35be development releases.  Even numbers (1.4,1.6,1.8) are stable
36releases.  The current 1.3 effort is working to produce a stable 2.0
37release.  A stable 2.0 release will not be made until it can
38accompanied by fully updated documentation.  In the meantime, we will
39continue to make periodic 1.3.x releases.
40
41We need your help!
42------------------
43Even if you are perfectly happy with SWIG-1.1, we can still use your
44feedback.  First, we like to know about compilation problems and other
45issues concerning the building of SWIG.  Second, if SWIG-1.3 is unable
46to compile your old interface files, we would like to get information
47about the features you are using.  This information will help us find
48bugs in the SWIG-1.3 release, develop techniques for supporting
49backwards compatibility, and write documentation that addresses
50specific issues related to migrating from SWIG-1.1 to SWIG-1.3.
51
52We are also looking for volunteers who would like to work on various
53aspects of SWIG development.  SWIG is an unfunded project that would
54not exist without volunteers.  We are also looking for the developers
55of other SWIG language modules.  If you have developed a SWIG module
56and would like to see it incorporated into the new release, please
57contact us to obtain SWIG-CVS access.  We are also more than willing
58to help port your module from SWIG-1.1 to SWIG-1.3.  Please send email
59to beazley@cs.uchicago.edu for further information.
60
61Please report problems with this release to the swig-dev mailing list,
62details at http://www.swig.org/mail.html.
63
64--- The SWIG Developers
65