Re: System.Time.Clock Design Issues

On Thursday 03 February 2005 18:42, Marcin 'Qrczak' Kowalczyk wrote:

"Udo Stenzel" writes:

...

Therefore, TAI + calendar + (optional) a fixed offset.

What am I missing?

That you don't know the correct offset.

If a program begins miscalculating the time when it's run 6 months after the Haskell compiler it was compiled with was been updated, and thus programs compiled using different versions of the compiler interpret the same timestamp differently, this makes no sense.

No problem if the leap second table used is a parameter of the conversion. Ben -- "The CIA is Wallstreet. Wallstreet is the CIA." (Mike Ruppert)