unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: emacs-devel@gnu.org
Subject: Re: Represent NTP's origin time
Date: Thu, 15 Apr 2021 08:40:22 -0400	[thread overview]
Message-ID: <jwvpmyvu3tx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <umtu00x74@gentoo.org> (Ulrich Mueller's message of "Thu, 15 Apr 2021 10:27:27 +0200")

>> NTP represents time stamps by counting seconds from January 1 1900, but
>> my Emacs doesn't seem to be able to represent this:
>
>>     (encode-time (parse-time-string "1902-01-01T00:00-00:00"))
>>     => (-32745 59520)
>>     (encode-time (parse-time-string "1900-01-01T00:00-00:00"))
>>     => (error "Specified time is not representable")
>
>> Do we have some "standard" workaround?
>
> Overflow in the underlying mktime(3) or mktime_z(3)? Are there still
> systems around where time_t has only 32 bits?

AFAIK all GNU/Linux i386 installations do.  Nowadays amd64 is more
common, but most of my machines are still running an i386 image and I'm
pretty sure I'm not the only one.

Also all armhf GNU/Linux systems do, and machines for which this is the
main/sole option are still being produced.

So, getting back to the question: Do we have some "standard" workaround?
I don't actually need to represent times from the early 20th century,
but I need to compute NTP timestamps.  I can come up with my own
workaround (e.g. hardcoding as a "magic constant" the number of seconds
between NTP's origin time and some arbitrary other origin time of my
choosing which 32bit systems can represent), but I was hoping we already
have something like that somewhere.


        Stefan




  parent reply	other threads:[~2021-04-15 12:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15  4:00 Represent NTP's origin time Stefan Monnier
2021-04-15  8:06 ` Andreas Schwab
2021-04-15  8:22   ` Gregory Heytings
2021-04-15  8:27 ` Ulrich Mueller
2021-04-15  8:30   ` Eli Zaretskii
2021-04-15 12:40   ` Stefan Monnier [this message]
2021-04-15 12:56     ` Andreas Schwab
2021-04-15 13:39       ` Stefan Monnier
2021-04-15 13:41     ` Ulrich Mueller
2021-04-15 13:44       ` Stefan Monnier
2021-04-15 14:06     ` Gregory Heytings
2021-04-15 14:51       ` Stefan Monnier
2021-04-15 19:12 ` Achim Gratz
2021-04-16  7:06   ` tomas
2021-04-17  3:53   ` Richard Stallman
2021-04-17  7:30     ` tomas
2021-04-17 13:44   ` Achim Gratz
2021-04-17 14:09     ` tomas
2021-04-17 14:23       ` Stefan Monnier
2021-04-17 14:55       ` Achim Gratz
2021-04-17 15:27         ` tomas
2021-04-17 16:20           ` Achim Gratz
2021-04-17 16:54           ` [OFFTOPIC] " Stefan Monnier
2021-04-17 20:00             ` tomas
2021-04-17 20:31               ` Stefan Monnier

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvpmyvu3tx.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=ulm@gentoo.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).