William A. Rowe, Jr. wrote:
Ronen Mizrahi wrote:Thank you for your response. The os error is not set in this case. According to the documentation on MSDN only when the return value of WaitForSingleObject() is WAIT_FAILED will an error be set. I supposed this is why the patch I suggest is already the current implementation for thread mutexes.Then I'm +1 on this patch for 2.2.2 and 0.9.7, but would like a second set of eyes before I commit it across trunk and those branches.
