Reference documentation for deal.II version 9.0.0
|
#include <deal.II/base/thread_management.h>
Public Member Functions | |
ScopedLock (DummyThreadMutex &) | |
~ScopedLock () | |
Scoped lock class. When you declare an object of this type, you have to pass it a mutex, which is locked in the constructor of this class and unlocked in the destructor. The lock is thus held during the entire lifetime of this object, i.e. until the end of the present scope, which explains where the name comes from. This pattern of using locks with mutexes follows the resource-acquisition-is-initialization pattern, and was used first for mutexes by Doug Schmidt. It has the advantage that locking a mutex this way is thread-safe, i.e. when an exception is thrown between the locking and unlocking point, the destructor makes sure that the mutex is unlocked; this would not automatically be the case when you lock and unlock the mutex "by hand", i.e. using Mutex::acquire() and Mutex::release().
Definition at line 95 of file thread_management.h.
|
inline |
Constructor. Lock the mutex. Since this is a dummy mutex class, this of course does nothing.
Definition at line 102 of file thread_management.h.
|
inline |
Destructor. Unlock the mutex. Since this is a dummy mutex class, this of course does nothing. We still don't declare it as 'default' to avoid warnings about objects of this class being unused.
Definition at line 109 of file thread_management.h.