RE: [boost] Time interfaces threads/file (was Design for a file s ystem library)

From: Darryl Green (green_at_[hidden])
Date: 2002-02-26 01:23:18

> -----Original Message-----
> From: Jeff Garland [mailto:jeff_at_[hidden]]
> Sent: Tuesday, 26 February 2002 2:43 AM
> Since GDTL supports the concept of multiple time 
> systems for different
> purposes, I'd like to gather the specific requirements for threads and
> filesystems.  Here's what I see from the current file 
> discussion and the current
> threads library:
> 
> * represent time durations (eg: 01:02:03.0000001) (thread only)
> * convert durations to counts a different resolutions (micro, 
> nano, etc) (thread
> only)
> * represent time points  (eg: 2002-02-25 08:00:00.0000001) (both)
> * represent time points with resolutions down to nano-seconds (both)
> * provisions for platforms that don't support nano-seconds (both)
> * get the current time point from the clock (both)
> * add durations to a time point (thread only)
> * compare timepoints  (eg: > < == !=) (both)
> * compare durations   (eg: > < == !=) (thread only)
> * ability output a time point to a string (file only -- clients)
> * a desire to minimize the dependencies
> 

One thing I don't see explicit mentioned here is the concept of a monotonic
clock as per IEEE Std 1003.1-2001. Is a clock type which deals with elapsed
time and is unaffected by changes to the system time supported?