Boost logo

Boost-Commit :

From: fmhess_at_[hidden]
Date: 2008-03-12 11:39:21

Author: fmhess
Date: 2008-03-12 11:39:21 EDT (Wed, 12 Mar 2008)
New Revision: 43575

Added some notes about details of blocking a connection
that is being run concurrently.

Text files modified:
   sandbox/thread_safe_signals/libs/thread_safe_signals/doc/reference/shared_connection_block.xml | 10 ++++++++++
   1 files changed, 10 insertions(+), 0 deletions(-)

Modified: sandbox/thread_safe_signals/libs/thread_safe_signals/doc/reference/shared_connection_block.xml
--- sandbox/thread_safe_signals/libs/thread_safe_signals/doc/reference/shared_connection_block.xml (original)
+++ sandbox/thread_safe_signals/libs/thread_safe_signals/doc/reference/shared_connection_block.xml 2008-03-12 11:39:21 EDT (Wed, 12 Mar 2008)
@@ -23,6 +23,16 @@
           after the <classname>connection</classname> object it was constructed
           from has been destroyed, or the connection it references has been
+ <para>
+ Note, blocking a connection does not guarantee the associated slot
+ has finished execution if it is already in the process of being run
+ when the connection block goes into effect. This is similar
+ to the behaviour of disconnect, in that blocking a connection
+ will not wait for the connection's associated slot to complete execution.
+ This situation may arise in a multi-threaded environment if the
+ connection block goes into effect concurrently with signal invocation,
+ or in a single-threaded environment if a slot blocks its own
+ connection.

Boost-Commit list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at