std.date

[Daniel Gibson]

Kagamin schrieb:
> Daniel Gibson Wrote:
> 
>>> I think, it's ok, computers work with nominal time and synchronize with world as needed. Hardly you can catch a bug with leap seconds.
>> As long as you're not Oracle and your enterprise clusterware crap reboots:
>> http://www.theregister.co.uk/2009/01/07/oracle_leap_second/
> 
> Synchronization can fail if the code asserts that number of seconds is not greater than 59 (Jonathan's lib does the same, I think). Is it the cause?

How are leap seconds handled on a computer anyway? Does the clock really count 
to 60 seconds (instead of 59) before the next minute starts, or is the clock 
just slowed down a bit (like it's - IIRC - done when changing the time with NTP 
or such)?