Boost :

Date view	Thread view	Subject view	Author view

From: Anthony Williams (anthony_w.geo_at_[hidden])
Date: 2007-11-28 07:26:12

Next message: James Talbut: "[boost] ASIO: Why does do_one use a one second timeout and loop whan called in blocking mode?"
Previous message: Anthony Williams: "Re: [boost] Boost Threads Condition may block forever on clockchange"
In reply to: Anthony Williams: "Re: [boost] Boost Threads Condition may block forever on clockchange"
Next in thread: Johan Nilsson: "Re: [boost] Boost Threads Condition may block forever on clockchange"

Anthony Williams <anthony_w.geo_at_[hidden]> writes:

> On Windows, we could use the System Up Time performance Counter, but I'm not
> sure what the resolution is.

It appears that the counter is provided as a number of 100ns (like FILETIME),
but it is not updated that fast --- it appears to be only updated every few
milliseconds on my system.

Also, it's not available on Windows 9x.

Anthony

-- 
Anthony Williams
Just Software Solutions Ltd - http://www.justsoftwaresolutions.co.uk
Registered in England, Company Number 5478976.
Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL

Next message: James Talbut: "[boost] ASIO: Why does do_one use a one second timeout and loop whan called in blocking mode?"
Previous message: Anthony Williams: "Re: [boost] Boost Threads Condition may block forever on clockchange"
In reply to: Anthony Williams: "Re: [boost] Boost Threads Condition may block forever on clockchange"
Next in thread: Johan Nilsson: "Re: [boost] Boost Threads Condition may block forever on clockchange"

Date view	Thread view	Subject view	Author view

Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk