File: condition.html

package info (click to toggle)
boost 1.27.0-3
  • links: PTS
  • area: main
  • in suites: woody
  • size: 19,908 kB
  • ctags: 26,546
  • sloc: cpp: 122,225; ansic: 10,956; python: 4,412; sh: 855; yacc: 803; makefile: 257; perl: 165; lex: 90; csh: 6
file content (338 lines) | stat: -rw-r--r-- 11,793 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
<html>
    <head>
        <meta http-equiv="Content-Type" content=
        "text/html; charset=iso-8859-1">
        <meta name="keywords" content="threads, BTL, thread library, C++">
        <link rel="stylesheet" type="text/css" href="styles.css">

        <title>Boost.Threads, condition</title>
    </head>

    <body bgcolor="#ffffff" link="#0000ff" vlink="#800080" text="#000000">
        <table summary="header" border="0" cellpadding="7" cellspacing="0"
        width="100%">
            <tr>
                <td valign="top" width="300">
                    <h3><img height="86" alt="C++ Boost" src=
                    "../../../c++boost.gif" width="277"></h3>
                </td>

                <td valign="top">
                    <h1 align="center">Boost.Threads</h1>

                    <h2 align="center">condition</h2>
                </td>
            </tr>
        </table>
        <hr>

        <p><a href="#Introduction">Introduction</a><br>
         <a href="#Header">Header</a><br>
         <a href="#Synopsis">Synopsis</a><br>
         <a href="#Members">Members</a><br>
         <a href="#Example">Example</a></p>

        <h2><a name="Introduction">Introduction</a></h2>

        <p>An object of class <code>condition</code> is a synchronization
        primitive used to cause a thread to wait until a particular shared-data
        condition (or time) is met. A <code>condition</code> object is always
        used in conjunction with a mutex object modeling a <a href=
        "mutex_concept.html">Mutex Concept</a>. The mutex must be locked prior
        to waiting on the <code>condition</code>, which is ensured by passing a
        lock object modeling a <a href="lock_concept.html">Lock Concept</a> to
        the <code>condition</code> object&#39;s <code>wait</code> functions.
        While the thread is waiting on the <code>condition</code> object, the
        mutex associated with the lock is unlocked. When the thread returns
        from a call to one of the <code>condition</code> object&#39;s <code>
        wait</code> functions, the mutex is again locked. The tricky
        lock/unlock/lock sequence is performed automatically by the <code>
        condition</code> object&#39;s <code>wait</code> functions.</p>

        <p>The <code>condition</code> type is often used to implement the <i>
        Monitor Object</i> and other important patterns. See <a href=
        "bibliography.html#Schmidt-00">[Schmidt-00]</a> and <a href=
        "bibliography.html#Hoare-74">[Hoare 74]</a>. Monitors are one of the
        most important patterns for creating reliable multithreaded
        programs.</p>

        <p>See <a href="definitions.html">Formal Definitions</a> for
        definitions of thread states <a href="definitions.html#state">
        blocked</a> and <a href="definitions.html#state">ready</a>. Note that
        &quot;waiting&quot; is a synonym for blocked.</p>

        <h2><a name="Header">Header</a></h2>
<pre>
#include <a href=
"../../../boost/thread/condition.hpp">&lt;boost/thread/condition.hpp&gt;</a>
</pre>

        <h2><a name="Synopsis">Synopsis</a></h2>
<pre>
namespace boost { 

class condition : private <a href=
"../../utility/utility.htm#Class noncopyable">boost::noncopyable</a> // Exposition only.
   // Class condition meets the <a href=
"overview.html#NonCopyable">NonCopyable</a> requirement.
{
public:
   condition();
   ~condition();

   void notify_one();
   void notify_all();
   template &lt;typename <a href="scoped_lock.html">ScopedLock</a>&gt;
      void wait(<a href="scoped_lock.html">ScopedLock</a>&amp; lock);
   template &lt;typename <a href="scoped_lock.html">ScopedLock</a>, typename <a
href="http://www.sgi.com/tech/stl/Predicate.html">Predicate</a>&gt;
      void wait(<a href="scoped_lock.html">ScopedLock</a>&amp; lock, <a href=
"http://www.sgi.com/tech/stl/Predicate.html">Predicate</a> pred);
   template &lt;typename <a href="scoped_lock.html">ScopedLock</a>&gt;
      bool timed_wait(<a href=
"scoped_lock.html">ScopedLock</a>&amp; lock, const xtime&amp; xt);
   template &lt;typename <a href="scoped_lock.html">ScopedLock</a>, typename <a
href="http://www.sgi.com/tech/stl/Predicate.html">Predicate</a>&gt;
      bool timed_wait(<a href=
"scoped_lock.html">ScopedLock</a>&amp; lock, const xtime&amp; xt, <a href=
"http://www.sgi.com/tech/stl/Predicate.html">Predicate</a> pred);
};

} // namespace boost
</pre>

        <h2><a name="Members">Members</a></h2>
        <hr>

        <h3>Constructor</h3>
<pre>
condition();
</pre>

        <p><b>Effects:</b> Constructs a <code>condition</code>.</p>
        <hr>

        <h3>Destructor</h3>
<pre>
~condition();
</pre>

        <p><b>Effects:</b> Destroys <code>*this</code>.</p>
        <hr>

        <h3>notify_one</h3>
<pre>
void notify_one();
</pre>

        <p><b>Effects:</b> If there is a thread waiting on <code>*this</code>,
        change that thread&#39;s state to ready. Otherwise there is no
        effect.</p>

        <p><b>Notes:</b> If more that one thread is waiting on the condition,
        it is unspecified which is made ready.</p>
        <hr>

        <h3>notify_all</h3>
<pre>
void notify_all();
</pre>

        <p><b>Effects:</b> Change the state of all threads waiting on <code>
        *this</code> to ready. If there are no waiting threads, <code>
        notify_all()</code> has no effect.</p>
        <hr>

        <h3>wait</h3>
<pre>
template &lt;typename ScopedLock&gt;
   void wait(ScopedLock&amp; lock);
</pre>

        <p><b>Requires:</b> ScopedLock meets the <a href=
        "lock_concept.html#ScopedLock">ScopedLock</a> requirements.</p>

        <p><b>Effects:</b> Releases the lock on the <a href=
        "mutex_concept.html">mutex model</a> associated with <code>lock</code>,
        blocks the current thread of execution until readied by a call to
        <code>this-&gt;notify_one()</code> or <code>
        this-&gt;notify_all()</code>, and then reacquires the lock. All effects
        occur in an atomic fashion.</p>

        <p><b>Throws:</b> <code><a href="lock_error.html">lock_error</a></code>
        if <code>!lock.locked()</code></p>

        <p><b>Danger:</b> This version should always be used within a loop
        checking that the state logically associated with the <code>
        condition</code> has become true. Without the loop, race conditions can
        ensue due to possible &quot;spurious wake ups&quot;. The second version
        encapsulates this loop idiom internally and is generally the preferred
        method.</p>
<pre>
template &lt;typename ScopedLock, typename Pr&gt;
   void wait(ScopedLock&amp; lock, Pr pred);
</pre>

        <p><b>Requires:</b> ScopedLock meets the <a href=
        "lock_concept.html#ScopedLock">ScopedLock</a> requirements, return from
        <code>pred()</code> convertible to bool.</p>

        <p><b>Effects:</b> As if:</p>
        <code>&nbsp;&nbsp;&nbsp;while (!pred()) wait(lock)</code> 

        <p><b>Throws:</b> <code><a href="lock_error.html">lock_error</a></code>
        if <code>!lock.locked()</code></p>
        <hr>

        <h3>timed_wait</h3>
<pre>
template &lt;typename ScopedLock&gt;
   bool timed_wait(ScopedLock&amp; lock, const <a href=
"xtime.html">xtime</a>&amp; xt);
</pre>

        <p><b>Requires:</b> ScopedLock meets the <a href=
        "lock_concept.html#ScopedLock">ScopedLock</a>
        requirements.</p>

        <p><b>Effects:</b> Releases the lock on the <a href=
        "mutex_concept.html">mutex model</a> associated with the <code>
        lock</code>, blocks the current thread of execution until readied by a
        call to <code>this-&gt;notify_one()</code> or <code>
        this-&gt;notify_all()</code>, or until <code>xt</code>, and then
        reacquires the lock. All effects occur in an atomic fashion.</p>

        <p><b>Throws:</b> <code><a href="lock_error.html">lock_error</a></code>
        if <code>!lock.locked()</code></p>

        <p><b>Danger:</b> This version should always be used within a loop
        checking that the state logically associated with the <code>
        condition</code> has become true. Without the loop, race conditions can
        ensue due to &quot;spurious wake ups&quot;. The second version
        encapsulates this loop idiom internally and is generally the preferred
        method.</p>

        <p><b>Returns:</b> <code>false</code> if <code>xt</code> is reached,
        otherwise <code>true</code>.</p>
<pre>
template &lt;typename ScopedLock, typename Pr&gt;
   bool timed_wait(ScopedLock&amp; lock, const <a href=
"xtime.html">xtime</a>&amp; xt, Pr pred);
</pre>

        <p><b>Requires:</b> ScopedLock meets the <a href=
        "lock_concept.html#ScopedLock">ScopedLock</a> requirements,
        return from <code>pred()</code> convertible to bool.</p>

        <p><b>Effects:</b> As if:</p>
        <code>&nbsp;&nbsp;&nbsp;while (!pred())<br>
         &nbsp;&nbsp;&nbsp;{<br>
         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if (!timed_wait(lock, xt))<br>
         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;return
        false;<br>
         &nbsp;&nbsp;&nbsp;}</code> 

        <p><b>Throws:</b> <code><a href="lock_error.html">lock_error</a></code>
        if <code>!lock.locked()</code></p>

        <p><b>Returns:</b> <code>false</code> if <code>xt</code> is reached,
        otherwise <code>true</code>.</p>
        <hr>

        <h2><a name="Example">Example Usage</a></h2>
<pre>
#include &lt;iostream&gt;
#include &lt;vector&gt;
#include <a href="../../../boost/utility.hpp">&lt;boost/utility.hpp&gt;</a>
#include <a href=
"../../../boost/thread/condition.hpp">&lt;boost/thread/condition.hpp&gt;</a>
#include <a href=
"../../../boost/thread/thread.hpp">&lt;boost/thread/thread.hpp&gt;</a>

class bounded_buffer : private boost::noncopyable
{
public:
    typedef boost::mutex::scoped_lock lock;

    bounded_buffer(int n) : begin(0), end(0), buffered(0), circular_buf(n) { }

    void send (int m) {
        lock lk(monitor);
        while (buffered == circular_buf.size())
            buffer_not_full.wait(lk);
        circular_buf[end] = m;
        end = (end+1) % circular_buf.size();
        ++buffered;
        buffer_not_empty.notify_one();
    }
    int receive() {
        lock lk(monitor);
        while (buffered == 0)
            buffer_not_empty.wait(lk);
        int i = circular_buf[begin];
        begin = (begin+1) % circular_buf.size();
        --buffered;
        buffer_not_full.notify_one();
        return i;
    }

private:
    int begin, end, buffered;
    std::vector&lt;int&gt; circular_buf;
    boost::condition buffer_not_full, buffer_not_empty;
    boost::mutex monitor;
};

bounded_buffer buf(2);

void sender() {
    int n = 0;
    while (n &lt; 100) {
       buf.send(n);
       std::cout &lt;&lt; &quot;sent: &quot; &lt;&lt; n &lt;&lt; std::endl;
       ++n;
    }
    buf.send(-1);
}

void receiver() {
    int n;
    do {
       n = buf.receive();
       std::cout &lt;&lt; &quot;received: &quot; &lt;&lt; n &lt;&lt; std::endl;
    } while (n != -1); // -1 indicates end of buffer
}

int main(int, char*[])
{
    boost::thread thrd1(&amp;sender);
    boost::thread thrd2(&amp;receiver);
    thrd1.join();
    thrd2.join();
    return 0;
}
</pre>

        <p>Typical output (dependent on scheduling policies) is:</p>
<pre>
sent: 0
sent: 1
received: 0
received: 1
sent: 2
sent: 3
received: 2
received: 3
sent: 4
received: 4
</pre>
        <hr>

        <p>Revised 
        <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->05 November, 2001<!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>

        <p><i>&copy; Copyright <a href="mailto:williamkempf@hotmail.com">
        William E. Kempf</a> 2001 all rights reserved.</i></p>
    </body>
</html>