LightMutexDirect¶
-
class
LightMutexDirect
¶ This class implements a lightweight Mutex by making direct calls to the underlying implementation layer. It doesn’t perform any debugging operations.
Inheritance diagram
-
void
acquire
(void) const¶ Grabs the lightMutex if it is available. If it is not available, blocks until it becomes available, then grabs it. In either case, the function does not return until the lightMutex is held; you should then call unlock().
This method is considered const so that you can lock and unlock const lightMutexes, mainly to allow thread-safe access to otherwise const data.
Also see LightMutexHolder.
-
void
clear_name
(void)¶ The lightMutex name is only defined when compiling in DEBUG_THREADS mode.
-
bool
debug_is_locked
(void) const¶ Returns true if the current thread has locked the
LightMutex
, false otherwise. This method is only intended for use in debugging, hence the method name; in theLightMutexDirect
case, it always returns true, since there’s not a reliable way to determine this otherwise.
-
std::string
get_name
(void) const¶ The lightMutex name is only defined when compiling in DEBUG_THREADS mode.
-
bool
has_name
(void) const¶ The lightMutex name is only defined when compiling in DEBUG_THREADS mode.
-
void
output
(std::ostream &out) const¶ This method is declared virtual in LightMutexDebug, but non-virtual in
LightMutexDirect
.
-
void
release
(void) const¶ Releases the lightMutex. It is an error to call this if the lightMutex was not already locked.
This method is considered const so that you can lock and unlock const lightMutexes, mainly to allow thread-safe access to otherwise const data.
-
void
set_name
(std::string const &name)¶ The lightMutex name is only defined when compiling in DEBUG_THREADS mode.
-
void