added functions to read/write several elements at once (patch 754986)

[wxWidgets.git] / docs / latex / wx / mutex.tex

diff --git a/docs/latex/wx/mutex.tex b/docs/latex/wx/mutex.tex
index 348ae108c419bf3900586afeb27f1d264f3d903e..fd3058b666c095abf532c8ef3468a328c12aafd6 100644 (file)
--- a/docs/latex/wx/mutex.tex
+++ b/docs/latex/wx/mutex.tex
@@ -37,7 +37,7 @@ because during a new node addition the list integrity is temporarily broken
         s_mutexProtectingTheGlobalList->Unlock();
     }
 
         s_mutexProtectingTheGlobalList->Unlock();
     }
 

-    // return TRUE the given number is greater than all array elements
+    // return true the given number is greater than all array elements

     bool MyThread::IsGreater(int num)
     {
         // before using the list we must acquire the mutex
     bool MyThread::IsGreater(int num)
     {
         // before using the list we must acquire the mutex


@@ -47,16 +47,16 @@ because during a new node addition the list integrity is temporarily broken
         for ( size_t n = 0; n < count; n++ )
         {
             if ( s_data[n] > num )
         for ( size_t n = 0; n < count; n++ )
         {
             if ( s_data[n] > num )

-                return FALSE;
+                return false;

         }
 
         }
 

-        return TRUE;
+        return true;

     }
 \end{verbatim}
 }
 
 Notice how wxMutexLocker was used in the second function to ensure that the
     }
 \end{verbatim}
 }
 
 Notice how wxMutexLocker was used in the second function to ensure that the

-mutex is unlocked in any case: whether the function returns TRUE or FALSE
+mutex is unlocked in any case: whether the function returns true or false

 (because the destructor of the local object {\it lock} is always called). Using
 this class instead of directly using wxMutex is, in general safer and is even
 more so if your program uses C++ exceptions.
 (because the destructor of the local object {\it lock} is always called). Using
 this class instead of directly using wxMutex is, in general safer and is even
 more so if your program uses C++ exceptions.


@@ -88,12 +88,6 @@ Default constructor.
 
 Destroys the wxMutex object.
 
 
 Destroys the wxMutex object.
 

-\membersection{wxMutex::IsLocked}\label{wxmutexislocked}
-
-\constfunc{bool}{IsLocked}{\void}
-
-Returns TRUE if the mutex is locked, FALSE otherwise.
-

 \membersection{wxMutex::Lock}\label{wxmutexlock}
 
 \func{wxMutexError}{Lock}{\void}
 \membersection{wxMutex::Lock}\label{wxmutexlock}
 
 \func{wxMutexError}{Lock}{\void}