System.Time.Clock Design Issues

[Ketil Malde]

Seth Kurtzberg <seth at cql.com> writes:

> When you say [TAI is] "defined for all history and the future", does
> that mean literally what it says? 

Well, as it is only a clock (counting SI seconds), it is unambigously
defined.  It is not a calendar, so you need a separate calendar to
name days and years for you, and to perform the mapping between TAI's
seconds and calendar entities.

-kzm
-- 
If I haven't seen further, it is by standing in the footprints of giants