System.Time.Clock Design Issues

[Simon Marlow]

On 03 February 2005 10:44, Ashley Yakeley wrote:

> OK, so we have
> 
> * POSIX time
> 
> Can do accurate calculations on calendar times.
> Can store UTC times reliably.
> Cannot store TAI times reliably.
> Broken for all leap seconds.
> 
> * 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.
> 
> Which of these is better?

The point is that everything you can do with a POSIX time you can also
do with a calendar time, which we need anyway.  So why have a POSIX time
too?

Cheers,
	Simon