Re: [boost] Re: condition::notify_all

2003-02-18 Thread William E. Kempf

Michael Glassford said:
> Scott McCaskill wrote:
>> I was just looking at the win32 implementation of the
>> condition variable class in the thread library and
>> noticed something odd.  In version 1.7 of
>> condition.cpp, there is a bug fix for
>> condition::notify_one.  At the beginning of the
>> function, a mutex is acquired, but not all control
>> paths resulted in the mutex being released.  Part of
>> the fix involved making sure that the mutex is always
>> released.
>>
>> However, it looks like the same behavior still exists
>> in the current version of condition.cpp for notify_all
>> (win32)--not all control paths will release the mutex.
>>  Am I mistaken, or is this a bug?
>
> It looks the same to me. Any comment about this?

I somehow missed the original post here.  Now fixed in CVS.

-- 
William E. Kempf


___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost



[boost] Re: condition::notify_all

2003-02-18 Thread Michael Glassford
Scott McCaskill wrote:
> I was just looking at the win32 implementation of the
> condition variable class in the thread library and
> noticed something odd.  In version 1.7 of
> condition.cpp, there is a bug fix for
> condition::notify_one.  At the beginning of the
> function, a mutex is acquired, but not all control
> paths resulted in the mutex being released.  Part of
> the fix involved making sure that the mutex is always
> released.
>
> However, it looks like the same behavior still exists
> in the current version of condition.cpp for notify_all
> (win32)--not all control paths will release the mutex.
>  Am I mistaken, or is this a bug?

It looks the same to me. Any comment about this?



> --Scott McCaskill

Mike



___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost