SourcePro® API Reference Guide

 
Loading...
Searching...
No Matches
RWTPCValStackGuarded< Type > Class Template Reference

Last-in-first-out (LIFO) stack that provides producer-consumer synchronization semantics for exchanging guarded values between cooperating threads. More...

#include <rw/itc/RWTPCValStackGuarded.h>

Inheritance diagram for RWTPCValStackGuarded< Type >:
RWTPCValBufferBaseGuarded< Type, RWTGuardDecorator< Type > > RWTPCValBufferBaseDecorated< Type, RWTGuardDecorator< Type > > RWTPCValBufferBase< RWTGuardDecorator< Type > > RWPCBufferBase RWTMonitor< RWMutexLock >

Public Member Functions

 RWTPCValStackGuarded (size_t maxCapacity)
 
 RWTPCValStackGuarded (size_t maxCapacity, bool isOpen)
 
 RWTPCValStackGuarded (void)
 
 ~RWTPCValStackGuarded (void)
 
- Public Member Functions inherited from RWTPCValBufferBaseGuarded< Type, RWTGuardDecorator< Type > >
virtual ~RWTPCValBufferBaseGuarded (void)
 
RWWaitStatus peek (Type &result, unsigned long milliseconds)
 
Type peek (void)
 
RWWaitStatus read (Type &result, unsigned long milliseconds)
 
Type read (void)
 
bool tryPeek (Type &value)
 
bool tryRead (Type &value)
 
bool tryWrite (const Type &value, const RWTFunctor< bool()> &guard)
 
void write (const Type &value, const RWTFunctor< bool()> &guard)
 
RWWaitStatus write (const Type &value, const RWTFunctor< bool()> &guard, unsigned long milliseconds)
 
- Public Member Functions inherited from RWTPCValBufferBaseDecorated< Type, RWTGuardDecorator< Type > >
virtual ~RWTPCValBufferBaseDecorated (void)
 
RWWaitStatus peek (Type &result, unsigned long milliseconds)
 
Type peek (void)
 
RWWaitStatus read (Type &result, unsigned long milliseconds)
 
Type read (void)
 
bool tryPeek (Type &result)
 
bool tryRead (Type &result)
 
bool tryWrite (const Type &value)
 
void write (const Type &value)
 
RWWaitStatus write (const Type &value, unsigned long milliseconds)
 

Additional Inherited Members

- Protected Types inherited from RWTMonitor< RWMutexLock >
typedef RWTLockGuard< RWTMonitor< RWMutexLock > > LockGuard
 
typedef RWTTryLockGuard< RWTMonitor< RWMutexLock > > TryLockGuard
 
typedef RWTUnlockGuard< RWTMonitor< RWMutexLock > > UnlockGuard
 
- Protected Member Functions inherited from RWTPCValBufferBase< RWTGuardDecorator< Type > >
virtual ~RWTPCValBufferBase (void)
 
RWWaitStatus peek (Type &result, unsigned long milliseconds)
 
Type peek (void)
 
RWWaitStatus read (Type &result, unsigned long milliseconds)
 
Type read (void)
 
bool tryPeek (Type &result)
 
bool tryRead (Type &result)
 
bool tryWrite (const Type &value)
 
void write (const Type &value)
 
RWWaitStatus write (const Type &value, unsigned long milliseconds)
 
virtual ~RWPCBufferBase (void)
 
bool canRead (void) const
 
bool canWrite (void) const
 
void close (void)
 
size_t entries (void) const
 
void flush (void)
 
size_t getCapacity (void) const
 
RWTFunctor< void()> getCloseCallback (void) const
 
RWTFunctor< void()> getEmptyCallback (void) const
 
RWTFunctor< void()> getFullCallback (void) const
 
RWTFunctor< void()> getOpenCallback (void) const
 
bool isOpen (void) const
 
void open (void)
 
size_t setCapacity (size_t maxCapacity)
 
void setCloseCallback (const RWTFunctor< void()> &onCloseCallback)
 
void setEmptyCallback (const RWTFunctor< void()> &onEmptyCallback)
 
void setFullCallback (const RWTFunctor< void()> &onFullCallback)
 
void setOpenCallback (const RWTFunctor< void()> &onOpenCallback)
 
- Protected Member Functions inherited from RWTMonitor< RWMutexLock >
 RWTMonitor (const RWTMonitor< RWMutexLock > &second)
 
 RWTMonitor (RWStaticCtor)
 
 RWTMonitor (void)
 
 ~RWTMonitor (void)
 
void acquire (void)
 
bool isAcquired (void) const
 
RWTMonitor< RWMutexLock > & monitor (void) const
 
RWMutexLockmutex (void)
 
RWTMonitor< RWMutexLock > & operator= (const RWTMonitor< RWMutexLock > &)
 
void release (void)
 
bool tryAcquire (void)
 

Detailed Description

template<class Type>
class RWTPCValStackGuarded< Type >

RWTPCValStackGuarded is a last-in-first-out (LIFO) stack that provides producer-consumer synchronization semantics for exchanging guarded values between cooperating threads.

In the producer-consumer synchronization model, reader threads (consumers) are blocked while the stack is empty, and writer threads (producers) are blocked while the stack is full. The stack is considered full when the number of unread entries equals or exceeds some user-specified maximum capacity.

The write operations inherited by this class bind a guard functor to each value prior to storing that value in an internal buffer. A guard functor is used during read operations to determine whether the associated value is currently eligible for retrieval from the buffer.

Example
See the example given under RWTPCValQueueGuarded.

Constructor & Destructor Documentation

◆ RWTPCValStackGuarded() [1/3]

template<class Type >
RWTPCValStackGuarded< Type >::RWTPCValStackGuarded ( void )
inline

Constructs a value-based, guarded, producer-consumer stack instance.

The stack is open on construction and enforces no limit on the number of items in the stack.

◆ RWTPCValStackGuarded() [2/3]

template<class Type >
RWTPCValStackGuarded< Type >::RWTPCValStackGuarded ( size_t maxCapacity)
inline

Constructs a value-based, guarded, producer-consumer stack instance.

The parameter maxCapacity specifies the maximum number of unread entries to allow to accumulate within the stack. Once the number of entries in the stack equals this number, any thread attempting to write an additional entry is blocked until an entry is removed by a read() operation, or until the capacity is increased. A capacity of zero is used to indicate that the stack has no size limit other than that imposed by memory limitations, and that all write() operations should complete without blocking.

The stack is open on construction.

◆ RWTPCValStackGuarded() [3/3]

template<class Type >
RWTPCValStackGuarded< Type >::RWTPCValStackGuarded ( size_t maxCapacity,
bool isOpen )
inline

Constructs a value-based, guarded, producer-consumer stack instance.

The parameter maxCapacity specifies the maximum number of unread entries to allow to accumulate within the stack. Once the number of entries in the stack equals this number, any thread attempting to write an additional entry is blocked until an entry is removed by a read() operation, or until the capacity is increased. A capacity of zero is used to indicate that the stack has no size limit other than that imposed by memory limitations, and that all write() operations should complete without blocking.

The parameter isOpen is a bool value that specifies whether the stack should be initialized in the open state, true, or the closed state, false.

◆ ~RWTPCValStackGuarded()

template<class Type >
RWTPCValStackGuarded< Type >::~RWTPCValStackGuarded ( void )
inline

Destructor.

Copyright © 2024 Rogue Wave Software, Inc., a Perforce company. All Rights Reserved.