leap second insertions
One additional second is all one needs, no? Two leap seconds are never inserted adjacent to each other. So POSIX's 'struct timespec' suffices to >represent leap seconds, and there's no need for a new data type here, just new operations on the type. You could start by adding a new clock to >clock_gettime, a clock that respects leap seconds.
There has never been more than one leap second added in any one instance, but as far as I know, nothing precludes adding more than one at any one time. But, I daresay there would be a really significant event that would cause it, such as an asteroid strike that affect the day :) Nathan
Nathan Justus <nathan.justus@oracle.com> wrote:
There has never been more than one leap second added in any one instance, but as far as I know, nothing precludes adding more than one at any one time.
The specification TF.460 does not allow for more than one leap second at the end of each month. http://www.itu.int/dms_pubrec/itu-r/rec/tf/R-REC-TF.460-6-200202-I!!PDF-E.pd... Tony. -- f.anthony.n.finch <dot@dotat.at> http://dotat.at/ North Rockall: Westerly or southwesterly 7 to severe gale 9, occasionally storm 10. High or very high. Showers. Good, occasionally poor.
participants (2)
-
Nathan Justus -
Tony Finch