PageRenderTime 42ms CodeModel.GetById 15ms RepoModel.GetById 0ms app.codeStats 0ms

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