My experience says that leap seconds do not impact epoch time (note that after inserting 26 leap seconds, the epoch time at the top of a minute is still currently a multiple of 60, whether using UTC or not). And, when you think about it, they can't.

Leap seconds are not scheduled very far in advance but epoch times for years in the future have been being used for years in the past. So leap seconds can't impact (Unix-style) epoch time values else past calculations of future dates would become inaccurate.

My experience says that leap seconds do not impact epoch time ... And, when you think about it, they can't.

You missed the point. I was not describing a problem with epoch times per se; but rather my method of deriving them.

The loop relies upon hitting every minute so as to ensure it will terminate. When the required minute is reached.

---

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority". The enemy of (IT) success is complexity.

In the absence of evidence, opinion is indistinguishable from prejudice.

The code hits each minute by adding 60 to epoch time values. So a leap second can't cause that code to miss a particular minute. Had the code done something like sleep(60), then a negative leap second or even just a bit of the system being busy could trip it up.

- tye