Re: System.Time.Clock Design Issues

Ashley Yakeley wrote:

In summary:

Using TAI with a limited leap-second table is trading a simple kind of brokenness (all leap seconds) for a complicated kind (future leap seconds after some date).

Getting rid of it all and using CalendarTime means slower clock retrieval and calculations as well as time-zone uncertainty.

What would you recommend?

I dont see why a calinder time is slower... UTC would be just another instance of the Calendar class, and you can use specialised fast instances to do the calculations (call a C library) Keean.