]> git.saurik.com Git - wxWidgets.git/blame - docs/latex/wx/mutex.tex
Split up wxStream doc files; added wxTCP... files; added wxBusyCursor;
[wxWidgets.git] / docs / latex / wx / mutex.tex
CommitLineData
eaaa6a06
JS
1\section{\class{wxMutex}}\label{wxmutex}
2
6e6110ee
VZ
3A mutex object is a synchronization object whose state is set to signaled when
4it is not owned by any thread, and nonsignaled when it is owned. Its name comes
5from its usefulness in coordinating mutually-exclusive access to a shared
6resource. Only one thread at a time can own a mutex object.
7
8For example, when several thread use the data stored in the linked list,
9modifications to the list should be only allowed to one thread at a time
10because during a new node addition the list integrity is temporarily broken
11(this is also called {\it program invariant}).
12
13\wxheading{Example}
14
15{\small%
16\begin{verbatim}
17 // this variable has an "s_" prefix because it is static: seeing an "s_" in
18 // a multithreaded program is in general a good sign that you should use a
19 // mutex (or a critical section)
20 static wxMutex *s_mutexProtectingTheGlobalData;
21
22 // we store some numbers in this global array which is presumably used by
23 // several threads simultaneously
24 wxArrayInt s_data;
25
26 void MyThread::AddNewNode(int num)
27 {
28 // ensure that no other thread accesses the list
29 s_mutexProtectingTheGlobalList->Lock();
30
31 s_data.Add(num);
32
33 s_mutexProtectingTheGlobalList->Unlock();
34 }
35
36 // return TRUE the given number is greater than all array elements
37 bool MyThread::IsGreater(int num)
38 {
39 // before using the list we must acquire the mutex
40 wxMutexLocker lock(s_mutexProtectingTheGlobalData);
41
42 size_t count = s_data.Count();
43 for ( size_t n = 0; n < count; n++ )
44 {
45 if ( s_data[n] > num )
46 return FALSE;
47 }
48
49 return TRUE;
50 }
51\end{verbatim}
52}
53
54Notice how wxMutexLocker was used in the second function to ensure that the
55mutex is unlocked in any case: whether the function returns TRUE or FALSE
56(because the destructor of the local object {\it lock} is always called). Using
57this class instead of directly using wxMutex is, in general safer and is even
58more so if yoor program uses C++ exceptions.
eaaa6a06
JS
59
60\wxheading{Derived from}
61
62None.
63
64\wxheading{See also}
65
6e6110ee
VZ
66\helpref{wxThread}{wxthread}, \helpref{wxCondition}{wxcondition},
67\helpref{wxMutexLocker}{wxmutexlocker}, \helpref{wxCriticalSection}{wxcriticalsection}
eaaa6a06
JS
68
69\latexignore{\rtfignore{\wxheading{Members}}}
70
71\membersection{wxMutex::wxMutex}\label{wxmutexconstr}
72
73\func{}{wxMutex}{\void}
74
75Default constructor.
76
77\membersection{wxMutex::\destruct{wxMutex}}
78
79\func{}{\destruct{wxMutex}}{\void}
80
81Destroys the wxMutex object.
82
83\membersection{wxMutex::IsLocked}\label{wxmutexislocked}
84
85\constfunc{bool}{IsLocked}{\void}
86
87Returns TRUE if the mutex is locked, FALSE otherwise.
88
89\membersection{wxMutex::Lock}\label{wxmutexlock}
90
91\func{wxMutexError}{Lock}{\void}
92
93Locks the mutex object.
94
95\wxheading{Return value}
96
97One of:
98
99\twocolwidtha{7cm}
100\begin{twocollist}\itemsep=0pt
6e6110ee
VZ
101\twocolitem{{\bf wxMUTEX\_NO\_ERROR}}{There was no error.}
102\twocolitem{{\bf wxMUTEX\_DEAD\_LOCK}}{A deadlock situation was detected.}
103\twocolitem{{\bf wxMUTEX\_BUSY}}{The mutex is already locked by another thread.}
eaaa6a06
JS
104\end{twocollist}
105
106\membersection{wxMutex::TryLock}\label{wxmutextrylock}
107
108\func{wxMutexError}{TryLock}{\void}
109
110Tries to lock the mutex object. If it can't, returns immediately with an error.
111
112\wxheading{Return value}
113
114One of:
115
116\twocolwidtha{7cm}
117\begin{twocollist}\itemsep=0pt
6e6110ee
VZ
118\twocolitem{{\bf wxMUTEX\_NO\_ERROR}}{There was no error.}
119\twocolitem{{\bf wxMUTEX\_DEAD\_LOCK}}{A deadlock situation was detected.}
120\twocolitem{{\bf wxMUTEX\_BUSY}}{The mutex is already locked by another thread.}
eaaa6a06
JS
121\end{twocollist}
122
123\membersection{wxMutex::Unlock}\label{wxmutexunlock}
124
125\func{wxMutexError}{Unlock}{\void}
126
127Unlocks the mutex object.
128
129\wxheading{Return value}
130
131One of:
132
133\twocolwidtha{7cm}
134\begin{twocollist}\itemsep=0pt
6e6110ee
VZ
135\twocolitem{{\bf wxMUTEX\_NO\_ERROR}}{There was no error.}
136\twocolitem{{\bf wxMUTEX\_DEAD\_LOCK}}{A deadlock situation was detected.}
137\twocolitem{{\bf wxMUTEX\_BUSY}}{The mutex is already locked by another thread.}
138\twocolitem{{\bf wxMUTEX\_UNLOCKED}}{The calling thread tries to unlock an unlocked mutex.}
eaaa6a06
JS
139\end{twocollist}
140
141