Re: [boost] [thread] deprecating Mutex::scoped_lock and Mutex::scoped_try_lock and boost::condition

Subject: Re: [boost] [thread] deprecating Mutex::scoped_lock and Mutex::scoped_try_lock and boost::condition
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2012-10-20 07:13:49

On Saturday 20 October 2012 13:08:18 Vicente J. Botet Escriba wrote:
> Hi,
> 
> I would like to deprecate the following features in Boost.Thread:
> 
> * Mutex::scoped_lock and Mutex::scoped_try_lock so that we can make
> mutex types independent from locks.
>   The user should use instead unique_lock<Mutex> and the new public
> class try_unique_lock.

Is try_unique_lock a new lock type? How is it different from unique_lock with 
try_to_lock argument?

> * condition: This was there for forward compatibility since 1.35.
> The user should use instead condition_variable_any.
> 
> 
> What do you think?

I'm ok with it.