Date: 2007-11-23 16:04:26
I've noticed a strange change in behaviour when
condition is called with xtime parameter,
condition::timed_wait. If right after the condition is
called the clock is moved back the code never exits
from condition unless signalled, even moving the clock
back forward did not seem to fix the problem. The test
was done on Windows XP.
Is this desired behaviour or a bug? It seems strange
that the condition is based on the current time and
not just on a time offset.
Any help with resolving this would be really
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk