Re: [boost] [signals2] extended_slot_type bug with preferred syntax

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

In case anyone is trying to use extended_slot_type/connect_extended with the "preferred syntax" signal for the review, there is a bug with the default ExtendedSlotFunction template type parameter. Fix is in svn revision 49593:

https://svn.boost.org/trac/boost/changeset?new=49593%40sandbox%2Fthread_safe_signals%2Ftrunk%2Fboost&old=49585%40sandbox%2Fthread_safe_signals%2Ftrunk%2Fboost

The "portable syntax" signals are not affected. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFJELwa5vihyNWuA4URAueDAJ9V/2Bdpf2N6VWaUrjgWpyIvyH1mgCgrOP0 mJzCelYUnWTmNsoHzMPfKdY= =8bRd -----END PGP SIGNATURE----- _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Hi Frank, have you got some examples with the usage of the extended_slot_type / connect_extended? In your documentation there is no example. Franz