Anthony Williams wrote:
Making this change, the race condition goes away on one more platform using in the boost interface. It should also be considered that relative timeouts in the boost interface certainly eliminate a problem on a platform with a large market share relevant to many boost developers for better or worse ;-)
How does the race condition go away by making everyone use relative timeouts?
You no longer internally (invisible to the user of boost::thread) query the absolute time makes it go away for Windows. And setting the clock condition attribute CLOCK_MONOTONIC with POSIX would make it impossible there as far as I can tell, does it not?
Relative timeouts are now supported in most boost::thread interfaces. The thread docs are out of date: I am in the process of updating them.
Ah, good to know. I was indeed looking at the old documentation online... Thorsten