Logo Search packages:      
Sourcecode: pwlib version File versions  Download package

void PReadWriteMutex::StartWrite (  ) 

This function attempts to acquire the mutex for writing. This call may be nested and must have an equal number of EndWrite() calls for the mutex to be released.

Note, if the same thread had a read lock previous to this call then the read lock is automatically released and reacquired when EndWrite() is called, unless an EndRead() is called. The EndRead() and EndWrite() calls do not have to be strictly nested.

It should also be noted that a consequence of this is that another thread may acquire the write lock before the thread that previously had the read lock. Thus it is impossibly to go straight from a read lock to write lock without the possiblility of the object being changed and application logic should take this into account.

Definition at line 2469 of file osutils.cxx.

References PSemaphore::Wait().

Referenced by PSafeObject::LockReadWrite(), and PWriteWaitAndSignal::PWriteWaitAndSignal().

  // Get the nested thread info structure, create one it it doesn't exist
  Nest & nest = StartNest();

  // One more nested call to StartWrite() by this thread, note this does not
  // need to be mutexed as it is always in the context of a single thread.

  // If is a nested call to StartWrite() then simply return, the writer count
  // increment is all we haev to do.
  if (nest.writerCount > 1)

  // If have a read lock already in this thread then do the "real" unlock code
  // but do not change the lock count, calls to EndRead() will now just
  // decrement the count instead of doing the unlock (its already done!)
  if (nest.readerCount > 0)

  // Note in this gap another thread could grab the write lock, thus

  // Now do the text book write lock

  if (writerCount == 1)



Generated by  Doxygen 1.6.0   Back to index