Boost logo

Boost :

Subject: Re: [boost] [thread] deprecating Mutex::scoped_lock and Mutex::scoped_try_lock and boost::condition
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2012-10-20 12:07:56


Le 20/10/12 17:48, Vicente J. Botet Escriba a écrit :
> Le 20/10/12 17:35, Andrey Semashev a écrit :
>> On Saturday 20 October 2012 17:27:40 Vicente J. Botet Escriba wrote:
>>> Le 20/10/12 13:13, Andrey Semashev a écrit :
>>>> Is try_unique_lock a new lock type? How is it different from
>>>> unique_lock
>>>> with try_to_lock argument?
>>> The single difference is that the constructor will try to lock instead
>>> of lock the mutex. If nobody needs it I just deprecate
>>> Mutex::scoped_try_lock and signal in the doc that the user can use a
>>> unique_lock using the try_lock_t tag.
>> IMHO, there is no need for this separate lock type, the same can be
>> achieved
>> with unique_lock.
>>
>>
>>
> Thanks for you quick answers.
>

I have created a ticket to track this.
https://svn.boost.org/trac/boost/ticket/7537

Best,
Vicente


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk