Home | All Classes | Main Classes | Annotated | Grouped Classes | Functions |
The QMutex class provides access serialization between threads. More...
#include <qmutex.h>
The purpose of a QMutex is to protect an object, data structure or section of code so that only one thread can access it at a time (In Java terms, this is similar to the synchronized keyword). For example, say there is a method which prints a message to the user on two lines:
void someMethod() { qDebug("Hello"); qDebug("World"); }
If this method is called simultaneously from two threads then the following sequence could result:
Hello Hello World World
If we add a mutex:
QMutex mutex; void someMethod() { mutex.lock(); qDebug("Hello"); qDebug("World"); mutex.unlock(); }
In Java terms this would be:
void someMethod() { synchronized { qDebug("Hello"); qDebug("World"); } }
Then only one thread can execute someMethod at a time and the order of messages is always correct. This is a trivial example, of course, but applies to any other case where things need to happen in a particular sequence.
When you call lock() in a thread, other threads that try to call lock() in the same place will block until the thread that got the lock calls unlock(). A non-blocking alternative to lock() is tryLock().
See also Environment Classes and Threading.
See also unlock() and locked().
Warning: Due to differing implementations of recursive mutexes on various platforms, calling this function from the same thread that previously locked the mutex will return undefined results.
The mutex must be unlocked with unlock() before another thread can successfully lock it.
See also lock(), unlock() and locked().
This file is part of the Qt toolkit. Copyright © 1995-2002 Trolltech. All Rights Reserved.
Copyright © 2002 Trolltech | Trademarks | Qt version 3.0.4
|