Re: [boost] [thread] Expected behaviour of condition variablewaitwhen the mutex is not locked

From: vicente.botet (vicente.botet_at_[hidden])
Date: 2008-05-08 10:20:08

----- Original Message ----- 
From: "Peter Dimov" <pdimov_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Thursday, May 08, 2008 4:03 PM
Subject: Re: [boost] [thread] Expected behaviour of condition 
variablewaitwhen the mutex is not locked

> Frank Mori Hess:
>> On Thursday 08 May 2008 04:51 am, Anthony Williams wrote:
>>> To this end, unique_lock is default-constructible and movable, and
>>> supports
>>> lock and unlock operations.
>>
>> Since when is unique_lock default-constructible?  You just mean it has a
>> defer_lock_t constructor, right?
>
> It does have a default constructor. Movable types have to have an "empty"
> state in which to put the moved-from source, and the default constructor 
> of
> a movable type usually creates such an "empty" object.

This is right on the proposal, but not onthe Boost::thread library.

> (The proposed promise
> doesn't adhere to this "convention" though.)

Should it?
_____________________
Vicente Juan Botet Escriba