Re: [boost] Maintenance Patches and cleaning up trac

Subject: Re: [boost] Maintenance Patches and cleaning up trac
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2010-05-21 14:10:23

----- Original Message ----- 
From: "Anthony Williams" <anthony.ajw_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Friday, May 21, 2010 7:14 PM
Subject: Re: [boost] Maintenance Patches and cleaning up trac

> 
> "vicente.botet" <vicente.botet_at_[hidden]> writes:
> 
>> This one seems to be already on trunk 
>> #3231 boost::thread fails to compile with the sun CC compiler
> 
> Closed.
> 
>> This seems to be released
>> #2100 thread fails to compile with -fno-exceptions
> 
> Closed.
> 
>> These ones seems to be invalid
>> #3269 boost thread - mutex.lock() doesn't throw exception
> 
> Fixed on trunk.
> 
>> #3178 Sleep with negative time (clarify on the documentation)
> 
> Fixed on trunk.

Great. I was sure that once you toke a look at the Track system there will be a lot of Thread tickets that were closed.
 
>> This is a very old ticket that comes recurrently
>> #2330 thread::interrupt() can be lost if condition_variable::wait() in progress
>> #3735 thread_group::interrupt_all() is unreliable
>> #3960 condition_variable::timed_wait() cannot be interrupted 
> 
> This one is a pain. I'm not sure how to fix it :-(

#2330  propose something close to a solution. You can also change the documentation and state that wait doesn't a interruption point.

Best,
Vicente