From: Zefram <zefram@fysh.org>
To: 26164@debbugs.gnu.org
Subject: bug#26164: time-difference mishandles leap seconds
Date: Sat, 18 Mar 2017 22:41:26 +0000 [thread overview]
Message-ID: <20170318224126.GK6518@fysh.org> (raw)
Computing the duration of the period between two UTC times, using
SRFI-19 mechanisms:
scheme@(guile-user)> (use-modules (srfi srfi-19))
scheme@(guile-user)> (define t0 (date->time-utc (make-date 0 59 59 23 30 6 2012 0)))
scheme@(guile-user)> (define t1 (date->time-utc (make-date 0 1 0 0 1 7 2012 0)))
scheme@(guile-user)> (time-difference t1 t0)
$1 = #<time type: time-duration nanosecond: 0 second: 2>
The two times are 2012-06-30T23:59:59 and 2012-07-01T00:00:01, so at
first glance one would expect the duration to be 2 s as shown above,
the two seconds being 23:59:59 and 00:00:00. But in fact there was
a leap second 2012-06-30T23:59:60, so the duration of this period is
actually 3 s. The SRFI-19 library is aware of this leap second, and
will compute the duration correctly if it's translated into TAI:
scheme@(guile-user)> (time-difference (time-utc->time-tai t1) (time-utc->time-tai t0))
$2 = #<time type: time-duration nanosecond: 0 second: 3>
The original computation in UTC space should yield a result of 3 s,
not the 2 s that it did. Since 1972, the seconds of UTC are of exactly
the same duration as the seconds of TAI. (They're also phase-locked to
TAI seconds.) Thus the period of three TAI seconds is also a period of
three UTC seconds. It is not somehow squeezed into two UTC seconds.
-zefram
next reply other threads:[~2017-03-18 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 22:41 Zefram [this message]
2017-04-19 14:32 ` bug#26164: time-difference mishandles leap seconds Andy Wingo
2017-04-19 16:22 ` Zefram
2018-10-21 22:56 ` Mark H Weaver
2018-11-05 11:02 ` Zefram
2018-11-05 13:47 ` John Cowan
2018-11-05 20:46 ` Mark H Weaver
2018-11-06 0:12 ` Mark H Weaver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170318224126.GK6518@fysh.org \
--to=zefram@fysh.org \
--cc=26164@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).