-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Friday 07 November 2008 08:39 am, Franz Alt wrote:
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?
It is there to make the slot's connection available to it in a convenient and thread-safe way. Otherwise, the connection object is not available until after the slot has already been connected (and might get invoked by another thread). See this post for a more verbose rationale:
http://lists.boost.org/Archives/boost/2008/10/142995.php -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFJFFBD5vihyNWuA4URAvz7AJwOWLCzi2iC7IiEwVDnq6MZmdRjVgCg19Y+ yGgbiDExE63G3kLEFx5wppM= =f4zj -----END PGP SIGNATURE----- _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
In the documentation there is only one sentence about the extended slot. From a pure user point of view it's very confusing what is the advantage of the extended slots contrary to the normal ones. I think the documentation makes it not clear when to use what type of slot. Do you plan to update the documentation at this point? I've looked at the documentation for the word 'thread' and I've found it only three times. I think the normal user wants to know more detailed informations about the thread safe signals library at a thread context. Do you also plan to enrich the documentation here?