System.Time.Clock Design Issues

[John Meacham]

you forgot some vital ones

On Thu, Feb 03, 2005 at 02:43:50AM -0800, Ashley Yakeley wrote:
> * POSIX time
> 
> Can do accurate calculations on calendar times.
> Can store UTC times reliably.
> Cannot store TAI times reliably.
> Broken for all leap seconds.
cannot represent durations
undefined before 1970, muddy definition in the future.

> 
> * TAI time with limited leap-second table
> 
> Can do accurate calculations on calendar times.
> Cannot store UTC times reliably.
> Can store TAI times reliably.
> Broken for leap seconds after table runs out.
can represent durations
defined for all history and future

> 
> Which of these is better?

TAI is clearly superior.
        John

-- 
John Meacham - ⑆repetae.net⑆john⑈