[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Leap Second planned for 2016
- Subject: Leap Second planned for 2016
- From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks at vt.edu)
- Date: Sat, 09 Jul 2016 17:12:29 -0400
- In-reply-to: <CAAeewD9LXBngWYT-RZJhC-oP7O2=BEDDjiQMmqWYJeKyyTgiUw@mail.gmail.com>
- References: <[email protected]> <CA+M5dWbZM1kQx1dG6Ba_cEYOyH=f9X5vhuc6bmM6s8pCdbGx=g@mail.gmail.com> <[email protected]> <CAAeewD_kxj2g4=XaNk8jj5DCp8hEhtNY5JhAQesCyYGVy8Opew@mail.gmail.com> <[email protected]> <CAAeewD9LXBngWYT-RZJhC-oP7O2=BEDDjiQMmqWYJeKyyTgiUw@mail.gmail.com>
On Sat, 09 Jul 2016 12:14:03 +0300, Saku Ytti said:
> Check the implementation on your PC. This is why code is broken and
> people don't even know it's broken. You have to use monotonic time to
> measure passage of time, which is not particularly easy to do
> portable, in some languages.
It doesn't help that the POSIX standard doesn't represent leap seconds
anyplace, so any elapsed time calculation that crosses a leap second
is guaranteed to be wrong....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20160709/db8e6b9a/attachment.pgp>