System.Time.Clock Design Issues

[Ashley Yakeley]

> So what we have is a type that behaves like TAI for the past, but 
> POSIX time for the future, even though it's supposed to be TAI. Surely 
> it would be better to simply use POSIX time?

Also, if we ever do manage to extract real TAI from the system clock 
and use that for getClockTime, the situation is much worse: after a 
leap second, obtaining the UTC time (the most basic requirement of a 
time library) will be off by a second.

-- 
Ashley Yakeley, Seattle WA