PageRenderTime 65ms CodeModel.GetById 20ms app.highlight 38ms RepoModel.GetById 2ms app.codeStats 1ms

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

#
#! | 125 lines | 85 code | 40 blank | 0 comment | 0 complexity | 709401c5f11c6d3b3b9689be2784e63d MD5 | raw file
Possible License(s): LGPL-2.1, Cube, GPL-3.0, 0BSD, GPL-2.0
  1*** ANNOUNCE: SWIG 1.3.15 ***
  2
  3http://www.swig.org
  4
  5September 9, 2002
  6
  7We're pleased to announce SWIG 1.3.15, the latest installment in the
  8SWIG development effort.  SWIG-1.3.15 is mostly a bug-fix release to
  9SWIG-1.3.14.  The release includes a number of minor enhancements to
 10overloading, template handling, and C++ exception handling.
 11
 12What is SWIG?
 13-------------
 14SWIG is a software development tool that reads C/C++ header files and
 15generates the wrapper code needed to make C and C++ code accessible
 16from other languages including Perl, Python, Tcl, Ruby, PHP, Java,
 17Guile, Mzscheme, and Ocaml.  Major applications of SWIG include
 18generation of scripting language extension modules, rapid prototyping,
 19testing, and user interface development for large C/C++ systems. 
 20
 21New Features in 1.3.15
 22----------------------
 23* C++ overloading support *
 24
 25Several enhancements to overloading. SWIG can now properly dispatch
 26functions like this:
 27
 28    class Foo { };
 29    class Bar : public Foo { };
 30
 31    void spam(Foo *f);      /* Function involving base class */
 32    void spam(Bar *b);      /* Function involving derived class */
 33
 34SWIG also no longer issues a warning message for methods that
 35differ only by 'const'.  Instead, the non-const method is always
 36preferred.
 37
 38The dispatch code should be a little more efficient.
 39
 40Overloading is now also supported by the Guile module.
 41
 42* Automatic wrapping of exception specifiers *
 43
 44SWIG is now able to automatically catch exceptions included in
 45C++ exception specifiers.  For example:
 46
 47   void spam(int x) throw(MemoryError, IndexError);
 48
 49The default behavior is to simply return with an error that
 50indicates the type of C++ exception that occurred.  However,
 51the behavior can be redefined using a special "throws" typemap.
 52
 53* Bug fixes *
 54
 55Numerous bug fixes in many parts of SWIG.  A large number of
 56template-typedef related bugs have been fixed in this release.  See
 57the CHANGES file for details.
 58
 59Some words on backwards compatibility
 60-------------------------------------
 61SWIG-1.3.15 is pushing SWIG development in some exciting new directions.
 62Support for overloading, smart pointers, and other long requested
 63features have been added.  A large number of enhancements to existing
 64language modules have also been included.
 65
 66That said, this release represents work in progress and is not
 67guaranteed to be backwards compatible with older SWIG versions.
 68However, we hope that people will try the release and give us feedback
 69on the new additions.
 70
 71Availability:
 72-------------
 73The release is available for download on Sourceforge at
 74
 75     http://prdownloads.sourceforge.net/swig/swig-1.3.15.tar.gz
 76
 77Within the next day, a Windows version will also be made available at
 78
 79     http://prdownloads.sourceforge.net/swig/swigwin-1.3.15.zip
 80
 81Release numbers
 82---------------
 83With SWIG1.3, we are adopting an odd/even version numbering scheme for
 84SWIG.  Odd version numbers (1.3, 1.5, 1.7, etc...) are considered to
 85be development releases.  Even numbers (1.4,1.6,1.8) are stable
 86releases.  The current 1.3 effort is working to produce a stable 2.0
 87release.  A stable 2.0 release will not be made until it can
 88accompanied by fully updated documentation.  In the meantime, we will
 89continue to make periodic 1.3.x releases.
 90
 91We need your help!
 92------------------
 93Even if you are perfectly happy with SWIG1.1, we can still use your
 94feedback.  First, we like to know about compilation problems and other
 95issues concerning the building of SWIG.  Second, if SWIG1.3 is unable
 96to compile your old interface files, we would like to get information
 97about the features you are using.  This information will help us find
 98bugs in the SWIG1.3 release, develop techniques for supporting
 99backwards compatibility, and write documentation that addresses
100specific issues related to migrating from SWIG1.1 to SWIG1.3.
101
102We are also looking for volunteers who would like to work on various
103aspects of SWIG development.  SWIG is an unfunded project that would
104not exist without volunteers.  We are also looking for the developers
105of other SWIG language modules.  If you have developed a SWIG module
106and would like to see it incorporated into the new release, please
107contact us to obtain SWIG-CVS access.  We are also more than willing
108to help port your module from SWIG1.1 to SWIG1.3.  Please send email
109to beazley@cs.uchicago.edu for further information.
110
111Please report problems with this release to swig-dev@cs.uchicago.edu.
112
113--- The SWIG Developers
114
115
116
117
118
119
120
121
122
123
124
125