From: John Cowan <cowan@ccil.org>
To: Mark H Weaver <mhw@netris.org>
Cc: zefram@fysh.org, 26632@debbugs.gnu.org
Subject: bug#26632: TAI<->UTC conversion botches 1961 to 1971
Date: Wed, 24 Oct 2018 14:11:42 -0400 [thread overview]
Message-ID: <CAD2gp_Teq_Mp4LZQy+6YAvJYq+9=cz3y94VNCtyymMq69e8abg@mail.gmail.com> (raw)
In-Reply-To: <87zhv3yjhu.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
On Wed, Oct 24, 2018 at 1:58 AM Mark H Weaver <mhw@netris.org> wrote:
> This has to be examined somewhat indirectly, because SRFI-19 doesn't offer
> > any way to display a TAI time in its conventional form as a date-like
> > structure, nor to input a TAI time from such a structure.
>
I think that is as it should be. TAI time is a count of SI seconds from a
particular instant in time. It is not divided up into minutes, hours,
days, months, years, etc. I realize that this is often done, but I believe
it to be not actually meaningful. These terms apply to dynamical time and
also in a slightly different way to UTC, but they have little meaning for
TAI.
--
John Cowan http://vrici.lojban.org/~cowan cowan@ccil.org
"Mr. Lane, if you ever wish anything that I can do, all you will have
to do will be to send me a telegram asking and it will be done."
"Mr. Hearst, if you ever get a telegram from me asking you to do
anything, you can put the telegram down as a forgery."
[-- Attachment #2: Type: text/html, Size: 1589 bytes --]
next prev parent reply other threads:[~2018-10-24 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 1:02 bug#26632: TAI<->UTC conversion botches 1961 to 1971 Zefram
2018-10-24 5:57 ` Mark H Weaver
2018-10-24 18:11 ` John Cowan [this message]
2018-11-06 4:21 ` Zefram
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='CAD2gp_Teq_Mp4LZQy+6YAvJYq+9=cz3y94VNCtyymMq69e8abg@mail.gmail.com' \
--to=cowan@ccil.org \
--cc=26632@debbugs.gnu.org \
--cc=mhw@netris.org \
--cc=zefram@fysh.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).