Thank you for the reply.<br><br>To clarify things in my mind: <br>Should I pass the lock itself to cond.wait for safety/correctness, or because this way I will get the desired behavior?<br><br>Best Regards,<br>Panagiotis Foteinos<br>
<br><div class="gmail_quote">On Mon, Mar 28, 2011 at 6:20 PM, Steven Watanabe <span dir="ltr">&lt;<a href="mailto:watanabesj@gmail.com">watanabesj@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
AMDG<div class="im"><br>
<br>
On 03/28/2011 03:03 PM, Panagiotis Foteinos wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello users.<br>
<br>
Documentation says that cond.wait(mtx) blocks the current thread and invokes<br>
mtx.unlock().<br>
<br>
What if I want cond.wait(mtx) to call mtx.unlock_shared() instead? Is there<br>
any way to do so?<br>
<br>
</blockquote>
<br></div>
You should pass the unique_lock or shared_lock<br>
to cond.wait, instead of passing the mutex itself.<br>
<br>
In Christ,<br><font color="#888888">
Steven Watanabe<br>
_______________________________________________<br>
Boost-users mailing list<br>
<a href="mailto:Boost-users@lists.boost.org" target="_blank">Boost-users@lists.boost.org</a><br>
<a href="http://lists.boost.org/mailman/listinfo.cgi/boost-users" target="_blank">http://lists.boost.org/mailman/listinfo.cgi/boost-users</a><br>
</font></blockquote></div><br>