ACE 8.0.2
Loading...
Searching...
No Matches
Public Types | Public Member Functions | Private Attributes | List of all members
ACE_Reverse_Lock< ACE_LOCKING_MECHANISM > Class Template Reference

A reverse (or anti) lock. More...

#include <Reverse_Lock_T.h>

Inheritance diagram for ACE_Reverse_Lock< ACE_LOCKING_MECHANISM >:
Inheritance graph
[legend]
Collaboration diagram for ACE_Reverse_Lock< ACE_LOCKING_MECHANISM >:
Collaboration graph
[legend]

Public Types

typedef ACE_LOCKING_MECHANISM ACE_LOCK
 

Public Member Functions

 ACE_Reverse_Lock (ACE_LOCKING_MECHANISM &lock, ACE_Acquire_Method::METHOD_TYPE acquire_method=ACE_Acquire_Method::ACE_REGULAR)
 Constructor. All locking requests will be forwarded to lock.
 
virtual ~ACE_Reverse_Lock ()=default
 
virtual int acquire ()
 Release the lock.
 
virtual int tryacquire ()
 Release the lock.
 
virtual int release ()
 Acquire the lock.
 
virtual int acquire_read ()
 Release the lock.
 
virtual int acquire_write ()
 Release the lock.
 
virtual int tryacquire_read ()
 Release the lock.
 
virtual int tryacquire_write ()
 Release the lock.
 
virtual int tryacquire_write_upgrade ()
 Release the lock.
 
virtual int remove ()
 Explicitly destroy the lock.
 
- Public Member Functions inherited from ACE_Lock
 ACE_Lock ()
 CE needs a default constructor here.
 
virtual ~ACE_Lock ()=default
 Noop virtual destructor.
 

Private Attributes

ACE_LOCKING_MECHANISMlock_
 The concrete locking mechanism that all the methods delegate to.
 
ACE_Acquire_Method::METHOD_TYPE acquire_method_
 This indicates what kind of acquire method will be called.
 

Detailed Description

template<class ACE_LOCKING_MECHANISM>
class ACE_Reverse_Lock< ACE_LOCKING_MECHANISM >

A reverse (or anti) lock.

This is an interesting adapter class that changes a lock into a reverse lock, i.e., <acquire> on this class calls <release> on the lock, and <release> on this class calls <acquire> on the lock. One motivation for this class is when we temporarily want to release a lock (which we have already acquired) but then reacquire it soon after. An alternative design would be to add a Anti_Guard or Reverse_Guard class which would <release> on construction and <acquire> destruction. However, there are many varieties of the Guard class and this design choice would lead to at least 6 new classes. One new ACE_Reverse_Lock class seemed more reasonable.

Member Typedef Documentation

◆ ACE_LOCK

Constructor & Destructor Documentation

◆ ACE_Reverse_Lock()

Constructor. All locking requests will be forwarded to lock.

◆ ~ACE_Reverse_Lock()

Destructor. If <lock_> was not passed in by the user, it will be deleted.

Member Function Documentation

◆ acquire()

Release the lock.

Implements ACE_Lock.

◆ acquire_read()

int ACE_Reverse_Lock< ACE_LOCKING_MECHANISM >::acquire_read ( )
virtual

Release the lock.

Implements ACE_Lock.

◆ acquire_write()

int ACE_Reverse_Lock< ACE_LOCKING_MECHANISM >::acquire_write ( )
virtual

Release the lock.

Implements ACE_Lock.

◆ release()

Acquire the lock.

Implements ACE_Lock.

◆ remove()

Explicitly destroy the lock.

Implements ACE_Lock.

◆ tryacquire()

int ACE_Reverse_Lock< ACE_LOCKING_MECHANISM >::tryacquire ( )
virtual

Release the lock.

Implements ACE_Lock.

◆ tryacquire_read()

int ACE_Reverse_Lock< ACE_LOCKING_MECHANISM >::tryacquire_read ( )
virtual

Release the lock.

Implements ACE_Lock.

◆ tryacquire_write()

int ACE_Reverse_Lock< ACE_LOCKING_MECHANISM >::tryacquire_write ( )
virtual

Release the lock.

Implements ACE_Lock.

◆ tryacquire_write_upgrade()

int ACE_Reverse_Lock< ACE_LOCKING_MECHANISM >::tryacquire_write_upgrade ( )
virtual

Release the lock.

Implements ACE_Lock.

Member Data Documentation

◆ acquire_method_

This indicates what kind of acquire method will be called.

◆ lock_

The concrete locking mechanism that all the methods delegate to.


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