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

Subject: Re: [boost] [signals2] extended_slot_type bug with preferred syntax
From: Franz Alt (f.alt_at_[hidden])
Date: 2008-11-07 08:39:26

>
>
>------- Start of text attachment -------
>Content-Type: text/plain ; charset="iso-8859-1"
>Content-Transfer-Encoding: UUE
>Content-Disposition=inline
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On Thursday 06 November 2008 03:11 am, Franz Alt wrote:
>> have you got some examples with the usage of the extended_slot_type /
>> connect_extended? In your documentation there is no example.
>
>Attached is an example program.
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.6 (GNU/Linux)
>
>iD8DBQFJEwuq5vihyNWuA4URAkBpAKCoJo5GTm6MPc27FjsBBvx5OqjORgCfXx9i
>oL5Hbtr/v4NMjinkLWlosUk=
>=fETt
>-----END PGP SIGNATURE-----
>------- End of text attachment -------
>
>
>------- Start of text attachment -------
>Content-Type: text/plain ; charset="us-ascii"
>Content-Transfer-Encoding: UUE
>MIME-Version=1.0
>Content-Disposition=inline
>
>_______________________________________________
>Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>------- End of text attachment -------

Hi,

what advantages has an extended slot contrary to a normal slot? I've look at the
libraries source code and at your example but I don't have the feeling that the extended
slots are much "better" than the normal ones. Is there a special case for the extended
slot?

Franz