summaryrefslogtreecommitdiffstats
path: root/src/corelib/doc
diff options
context:
space:
mode:
authorSze Howe Koh <szehowe.koh@gmail.com>2013-10-03 22:39:00 +0800
committerThe Qt Project <gerrit-noreply@qt-project.org>2013-10-06 01:08:27 +0200
commit2524cafc8e84862d14fcb57ab68720d04de5659a (patch)
tree17aaff6b9a5e7145188463a7c10822ef49a05659 /src/corelib/doc
parenta15bc0e714539c3dca8476254780e645bbbe1a12 (diff)
Doc: Remove convoluted details of uncommon QMutex use case
Change-Id: If80068f44fef7ab0692b9dad99aa7e1a30cb72a6 Reviewed-by: Olivier Goffart <ogoffart@woboq.com> Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Diffstat (limited to 'src/corelib/doc')
-rw-r--r--src/corelib/doc/src/threads-basics.qdoc9
1 files changed, 0 insertions, 9 deletions
diff --git a/src/corelib/doc/src/threads-basics.qdoc b/src/corelib/doc/src/threads-basics.qdoc
index 5d6e0f6ef1..3cf2e66682 100644
--- a/src/corelib/doc/src/threads-basics.qdoc
+++ b/src/corelib/doc/src/threads-basics.qdoc
@@ -266,15 +266,6 @@
used to make a method thread safe. Most Qt methods aren't thread safe
because there is always a performance penalty when using mutexes.
- It isn't always possible to lock and unlock a mutex in a method. Sometimes
- the need to lock spans several calls. For example, modifying a container
- with an iterator requires a sequence of several calls which should not be
- interrupted by other threads. In such a scenario, locking can be achieved
- with a mutex that is kept outside of the object to be manipulated. With an
- external mutex, the duration of locking can be adjusted to the needs of the
- operation. One disadvantage is that external mutexes aid locking, but do
- not enforce it because users of the object may forget to use it.
-
\section2 Dealing with Asynchronous Execution
One way to obtain a worker thread's result is by waiting for the thread