# ReMutex

from pandac.PandaModules import ReMutex

## Inheritance:

ReMutex: ReMutexDirect
ReMutexDirect:

## Methods of ReMutexDirect:

debugIsLocked
elevateLock
lock
output
release

debugIsLocked bool ReMutexDirect::debug_is_locked(void) const; Description: Returns true if the current thread has locked the ReMutex, false otherwise. This method is only intended for use in debugging, hence the method name; in the ReMutexDirect case, it always returns true, since there's not a reliable way to determine this otherwise.

elevateLock void ReMutexDirect::elevate_lock(void) const; Description: This method increments the lock count, assuming the calling thread already holds the lock. After this call, release() will need to be called one additional time to release the lock. This method really performs the same function as lock(), but it offers a potential (slight) performance benefit when the calling thread knows that it already holds the lock. It is an error to call this when the calling thread does not hold the lock.

lock void ReMutexDirect::lock(void) const; Description: Grabs the reMutex 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 reMutex is held; you should then call unlock(). This method is considered const so that you can lock and unlock const reMutexes, mainly to allow thread-safe access to otherwise const data. Also see ReMutexHolder. Description: This variant on lock() accepts the current thread as a parameter, if it is already known, as an optimization.

output void ReMutexDirect::output(ostream &out) const; Description: This method is declared virtual in MutexDebug, but non-virtual in ReMutexDirect.

release void ReMutexDirect::release(void) const; Description: Releases the reMutex. It is an error to call this if the reMutex was not already locked. This method is considered const so that you can lock and unlock const reMutexes, mainly to allow thread-safe access to otherwise const data.