From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ihor Radchenko <yantar92@gmail.com>, emacs-devel@gnu.org
Subject: Re: What were the Emacs versions with dates limited to 1970 .. 2037 year range?
Date: Sun, 12 Jun 2022 10:21:39 -0400 [thread overview]
Message-ID: <jwvk09matgf.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83r13uurom.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 12 Jun 2022 13:00:57 +0300")
Eli Zaretskii [2022-06-12 13:00:57] wrote:
>> > Any 32-bit build of Emacs is potentially prone to this problem,
>> > depending on what time-related APIs it is using. If time_t is a
>> > 32-bit type, this problem will still exist.
>>
>> Thanks for the clarification!
>>
>> I am now wondering if it is soon going to be the time to do something
>> about it. 2037 is getting closer and the 32-bit limitation may become a
>> real issue for the 32-bit Emacs builds.
>
> Yes, at some point in the not-so-distant future we will have to face
> the issue.
I thought there was nothing to be done on our side: we only suffer from
the limitations that are imposed by the libc (and only when the value
needs to be passed to libc), and as soon as the underlying OS/libc is
updated to avoid those problems, the problem also disappears in Emacs.
Stefan
next prev parent reply other threads:[~2022-06-12 14:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 9:13 What were the Emacs versions with dates limited to 1970 .. 2037 year range? Ihor Radchenko
2022-06-12 9:22 ` Eli Zaretskii
2022-06-12 9:51 ` Ihor Radchenko
2022-06-12 10:00 ` Eli Zaretskii
2022-06-12 14:21 ` Stefan Monnier [this message]
2022-06-12 14:41 ` Eli Zaretskii
2022-06-13 0:30 ` Po Lu
2022-06-13 2:37 ` Eli Zaretskii
2022-06-13 9:25 ` Stefan Kangas
2022-06-13 11:49 ` Eli Zaretskii
2022-06-13 13:19 ` Stefan Monnier
2022-06-13 13:29 ` Eli Zaretskii
2022-06-13 16:40 ` 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=jwvk09matgf.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yantar92@gmail.com \
/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).