C++0X Its about (y)time

This is the proposed ytime.

struct ytime { time_t tv_sec; unsigned long tv_nsec; };

This time representation would be used for both absolute and relative
time,
i.e. all time delays and would be returned by all standard-conforming
clocks.

This time representation would be used as an argument for sleep() and for
condition_variable::timed_wait().

Some points in favor of ytime:

     * simple

     * easy to monitor in a debugger

..  * maps easily to POSIX timespec and (deprecated) time_t

    * same time representation for absolute and relative time

Some points agains ytime

   * operations on ytime are difficult and error-prone because the time is
broken up into two fields instead of being a continuous count

   * operations and storage are less efficient than just a 'long long
count'
of nanoseconds since midnight, Jan 1, 1970 (overflows in 2262).

   * has the same "Year 2038" problem that time_t has.

   * unclear mapping to UTC or how leap-seconds are handled

   * same time representation for absolute and relative time

This representation is very similar to POSIX timespec, so many people
already have gained experience, good or bad.

More elaborate systems of clocks and time representations are possible,
but
please limit discussion to the ytime representation.

Do you think C++ should adopt ytime?

terry





-- 
      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]