[sigc] ANNOUNCE: libsigc++ 2.0.6



*** libsigc++ 2.0

libsigc++ implements a typesafe callback system for standard C++. It
allows you to define signals and to connect those signals to any
callback function, either global or a member function, regardless of
whether it is static or virtual.

libsigc++ is used by gtkmm to wrap the GTK+ signal system. It does not
depend on GTK or gtkmm.

Further information about the major release 2.0 is available on the
libsigc++ project home page: http://libsigc.sourceforge.net/


*** Changes:

2.0.6:

* Fixed a memory leak in sigc::slot.
* Fixed compilation for gcc-3.4.
* Fixed compilation for Intel C++ compiler (upgraded libtool).
* Fixed project files for MSVC .Net (Timothy M. Shead).
* Fixed segfaults when compiled with MSVC .Net 2003 (moved
 all calls to new and delete into non-inline library code).
* In the compatibility module use correct bound_mem_functor
 variants for const (volatile) methods when creating a slot.
* Minor documentation fix.
* Resolved bugs: #152327 #148744 #152323 #151404 #153143


*** Compatibility:

This release has not been tested for all supported platforms! It should
at least compile with:
- gcc >= 3.2
- cygwin (gcc >= 3.2)
- mingw32
- Microsoft Visual Studio .Net 2003
- Sun Forte C++ compiler >= 5.5
- Compaq C++ compiler
- Intel compiler
Please report any troubles you encounter with these compilers!
You are also invited to try a compiler that is not listed above.


*** Download:

libsigc++ is available for download here:
http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.0/
http://libsigc.sourceforge.net/

A reference documentation for libsigc++ 2.0 can be found here:
http://libsigc.sourceforge.net/libsigc2/docs/


*** Known issues:

* Compilation errors with gcc-3.2 have been reported.

* When the compatibility module is used with "using namespace SigC",
gcc-3.2 reports conflicts of SigC::slot() with struct sigc::slot.
A fishy work-around has been disabled to support the .Net compiler.

* Documentation of the lambda functionality is still incomplete.

* Examples for the "API improvements" section must be written and
uploaded to the web site.





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