Subject: Re: [boost] [Thread][Release] Boost.Thread and 1.45 release
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2010-10-28 13:35:09
----- Original Message -----
From: "Anthony Williams" <anthony.ajw_at_[hidden]>
Sent: Thursday, October 28, 2010 4:36 PM
Subject: [boost] [Thread][Release] Boost.Thread and 1.45 release
> I've fixed all the outstanding "showstopper" bugs in boost.thread on
> trunk (including the thread interruption issue, #2330), apart from #3847
> (https://svn.boost.org/trac/boost/ticket/3847) - "Unable to statically
> link thread lib on ia64"
I have take a look at the modification associated to this ticket #2330 thread::interrupt() can be lost if condition_variable::wait() in progress and I don't reach to understand why do you need to have an internal mutex on condition_variable. The associated patch don't modifies this point. The resolution don't states nothing more than the ticket has been solved but no how. Please could you explain this addition? Is this related to another ticket?
This will make condition_variable and condition_variable_any almost equivalent. What will be the adavantage to use condition_variable respect to condition_variable_any?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk