From: <tomas@tuxteam.de>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-devel@gnu.org
Subject: Re: Represent NTP's origin time
Date: Sat, 17 Apr 2021 16:09:51 +0200 [thread overview]
Message-ID: <20210417140951.GB726@tuxteam.de> (raw)
In-Reply-To: <8735vpyqir.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
On Sat, Apr 17, 2021 at 03:44:28PM +0200, Achim Gratz wrote:
> Achim Gratz writes:
> > Stefan Monnier writes:
> >> 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?
> >
> > Get off your 32bit system already?
>
> There have been responses that called this answer "unkind" or "snarky".
Only mildly so, from my side.
> It wasn't meant to be, I apologise for the impression that was likely
> created by being too brief [...]
I do understand the issues, but see below.
I replied (or so I thought) "in kind". A better reply would have
been: Emacs supports 32 bit platforms. Unless ending 32 bit
support is in the near-future, it'd be a good idea to think about
how to support a wider (possibly 64 bit) time_t even on a 32 bit
Emacs.
The *BSDs and Linux (beyond kernel 5.6ish) do support 64 bit time_t
in their 32 bit variants: perhaps this is an orientation.
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2021-04-17 14:09 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
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 [this message]
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=20210417140951.GB726@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=Stromeko@nexgo.de \
--cc=emacs-devel@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.
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).