Subject: [boost] [chrono] chrono/config.hpp enforces that time.h defines CLOCK_REALTIME; should it?
From: Krzysztof Czainski (1czajnik_at_[hidden])
Date: 2012-06-27 08:31:07
Suppose I want to use durations, and time_points with a user defined clock.
I don't want to use any clocks provided by Boost.Chrono.
My compiler provides a <time.h>, which doesn't define CLOCK_REALTIME, which
chrono/config.hpp reports as an error. This prevents me from using parts of
Chrono, that I believe don't depend on anything from <time.h>.
I am able to work around this by simply defining CLOCK_REALTIME. But I
would like to ask: Could Boost.Chrono allow using duration.hpp and
time_point.hpp in my case?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk