Panda3D
Public Member Functions | Friends | List of all members
ReMutexDirect Class Reference

This class implements a standard reMutex by making direct calls to the underlying implementation layer. More...

#include "reMutexDirect.h"

Inheritance diagram for ReMutexDirect:
ReMutex

Public Member Functions

void acquire () const
 Grabs the reMutex if it is available. More...
 
void acquire (Thread *current_thread) const
 This variant on acquire() accepts the current thread as a parameter, if it is already known, as an optimization. More...
 
void clear_name ()
 The mutex name is only defined when compiling in DEBUG_THREADS mode. More...
 
bool debug_is_locked () const
 Returns true if the current thread has locked the ReMutex, false otherwise. More...
 
void elevate_lock () const
 This method increments the lock count, assuming the calling thread already holds the lock. More...
 
string get_name () const
 The mutex name is only defined when compiling in DEBUG_THREADS mode. More...
 
bool has_name () const
 The mutex name is only defined when compiling in DEBUG_THREADS mode. More...
 
void output (ostream &out) const
 This method is declared virtual in MutexDebug, but non-virtual in ReMutexDirect. More...
 
void release () const
 Releases the reMutex. More...
 
void set_name (const string &name)
 The mutex name is only defined when compiling in DEBUG_THREADS mode. More...
 
bool try_acquire () const
 Returns immediately, with a true value indicating the mutex has been acquired, and false indicating it has not. More...
 
bool try_acquire (Thread *current_thread) const
 Returns immediately, with a true value indicating the mutex has been acquired, and false indicating it has not. More...
 

Friends

class LightReMutexDirect
 

Detailed Description

This class implements a standard reMutex by making direct calls to the underlying implementation layer.

It doesn't perform any debugging operations.

Definition at line 32 of file reMutexDirect.h.

Member Function Documentation

◆ acquire() [1/2]

void ReMutexDirect::acquire ( ) const
inline

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.

Definition at line 82 of file reMutexDirect.I.

Referenced by ReMutexHolder::ReMutexHolder().

◆ acquire() [2/2]

void ReMutexDirect::acquire ( Thread current_thread) const
inline

This variant on acquire() accepts the current thread as a parameter, if it is already known, as an optimization.

Definition at line 99 of file reMutexDirect.I.

References try_acquire().

◆ clear_name()

void ReMutexDirect::clear_name ( )
inline

The mutex name is only defined when compiling in DEBUG_THREADS mode.

Definition at line 219 of file reMutexDirect.I.

References has_name().

Referenced by set_name().

◆ debug_is_locked()

bool ReMutexDirect::debug_is_locked ( ) const
inline

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.

Definition at line 198 of file reMutexDirect.I.

References set_name().

Referenced by GraphicsEngine::do_cull(), and release().

◆ elevate_lock()

void ReMutexDirect::elevate_lock ( ) const
inline

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 acquire(), 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.

Definition at line 158 of file reMutexDirect.I.

References release().

Referenced by try_acquire().

◆ get_name()

string ReMutexDirect::get_name ( ) const
inline

The mutex name is only defined when compiling in DEBUG_THREADS mode.

Definition at line 240 of file reMutexDirect.I.

References Thread::get_current_thread().

Referenced by has_name().

◆ has_name()

bool ReMutexDirect::has_name ( ) const
inline

The mutex name is only defined when compiling in DEBUG_THREADS mode.

Definition at line 229 of file reMutexDirect.I.

References get_name().

Referenced by clear_name().

◆ output()

void ReMutexDirect::output ( ostream &  out) const

This method is declared virtual in MutexDebug, but non-virtual in ReMutexDirect.

Definition at line 27 of file reMutexDirect.cxx.

References Thread::get_current_thread().

◆ release()

void ReMutexDirect::release ( ) const
inline

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.

Definition at line 178 of file reMutexDirect.I.

References debug_is_locked().

Referenced by elevate_lock().

◆ set_name()

void ReMutexDirect::set_name ( const string &  name)
inline

The mutex name is only defined when compiling in DEBUG_THREADS mode.

Definition at line 209 of file reMutexDirect.I.

References clear_name().

Referenced by debug_is_locked().

◆ try_acquire() [1/2]

bool ReMutexDirect::try_acquire ( ) const
inline

Returns immediately, with a true value indicating the mutex has been acquired, and false indicating it has not.

Definition at line 116 of file reMutexDirect.I.

Referenced by acquire().

◆ try_acquire() [2/2]

bool ReMutexDirect::try_acquire ( Thread current_thread) const
inline

Returns immediately, with a true value indicating the mutex has been acquired, and false indicating it has not.

Definition at line 133 of file reMutexDirect.I.

References elevate_lock().


The documentation for this class was generated from the following files: