From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#32902: Add support for (TIMESTAMP . RESOLUTION) Lisp timestamps Date: Wed, 10 Oct 2018 06:49:03 +0300 Message-ID: <83o9c2xxzk.fsf@gnu.org> References: <83y3bh2gns.fsf@gnu.org> <13abcc70-0e5b-0d5f-fffc-9b146743a565@cs.ucla.edu> <83a7nt3dac.fsf@gnu.org> <8336th1w0l.fsf@gnu.org> <83va6dyx69.fsf@gnu.org> <838t37yx5g.fsf@gnu.org> <3f0bcf06-83f2-a0e9-c9ab-b06d65417afe@cs.ucla.edu> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1539143288 23632 195.159.176.226 (10 Oct 2018 03:48:08 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 10 Oct 2018 03:48:08 +0000 (UTC) Cc: 32902@debbugs.gnu.org To: Paul Eggert Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Oct 10 05:48:03 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gA5Tf-00061q-0E for geb-bug-gnu-emacs@m.gmane.org; Wed, 10 Oct 2018 05:48:03 +0200 Original-Received: from localhost ([::1]:54682 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gA5Vl-0002kB-Fx for geb-bug-gnu-emacs@m.gmane.org; Tue, 09 Oct 2018 23:50:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37295) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gA5Vd-0002k3-7j for bug-gnu-emacs@gnu.org; Tue, 09 Oct 2018 23:50:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gA5Va-0003o4-Gg for bug-gnu-emacs@gnu.org; Tue, 09 Oct 2018 23:50:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:38477) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gA5Va-0003nr-C3 for bug-gnu-emacs@gnu.org; Tue, 09 Oct 2018 23:50:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gA5Va-0001mp-7U for bug-gnu-emacs@gnu.org; Tue, 09 Oct 2018 23:50:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 10 Oct 2018 03:50:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32902 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 32902-submit@debbugs.gnu.org id=B32902.15391433576799 (code B ref 32902); Wed, 10 Oct 2018 03:50:02 +0000 Original-Received: (at 32902) by debbugs.gnu.org; 10 Oct 2018 03:49:17 +0000 Original-Received: from localhost ([127.0.0.1]:42735 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gA5Uq-0001lZ-VB for submit@debbugs.gnu.org; Tue, 09 Oct 2018 23:49:17 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:55792) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gA5Up-0001lF-A3 for 32902@debbugs.gnu.org; Tue, 09 Oct 2018 23:49:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gA5Uh-00037f-7a for 32902@debbugs.gnu.org; Tue, 09 Oct 2018 23:49:09 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:48973) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gA5Uh-00037V-2Z; Tue, 09 Oct 2018 23:49:07 -0400 Original-Received: from [176.228.60.248] (port=2659 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gA5Ug-0001Yn-LG; Tue, 09 Oct 2018 23:49:06 -0400 In-reply-to: <3f0bcf06-83f2-a0e9-c9ab-b06d65417afe@cs.ucla.edu> (message from Paul Eggert on Tue, 9 Oct 2018 13:15:57 -0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:151064 Archived-At: > Cc: 32902@debbugs.gnu.org > From: Paul Eggert > Date: Tue, 9 Oct 2018 13:15:57 -0700 > > >> Any of these would insulate the rest of Emacs from this glitch. > > The last two are undesirable, since it is generally expected of a > > single Windows binary to run on all supported systems; having 2 > > separate binaries is possible, but complicates the matters. > > > Alternative (2) should also let a single binary run on all supported > MS-Windows systems, unless I'm misunderstanding something. You are right, I wasn't paying attention. > The idea is that Emacs proper uses 64-bit time_t and only a small > part of w32*.c knows whether the MS-Windows API is using 32- or > 64-bit time_t. Emacs could do this by using "#define time_t long > long int" for most of Emacs, and having only the small part of > w32*.c worry about the conversion. Yes. Not sure about the "small" part, though: time_t appears in many libc functions ('stat' and 'fstat' come to mind), and we currently still use most of the structures defined in system headers which reference time_t values. > Also, don't we already have 2 separate binaries, one for 32-bit and one > for 64-bit MS-Windows? We do, but the 32-bit binaries are expected to run on 64-bit systems. We cannot avoid having the separate 64-bit binaries, whereas the additional 32-bit binaries are just a nuisance. Note that at least some of the support libraries might also need to be built twice, if time_t is used in their interfaces, directly or indirectly. > > Last time this came up, we decided not to drop support even for Windows 9X > > It's your decision since you're the maintainer, and if you want to spend > time porting to obsolete operating systems it's your time to spend. That > being said, there's vanishingly little real-world need to run the *very > latest* version of GNU Emacs on Windows XP and earlier and for security > reasons if the documentation for the latest Emacs version discusses > these older machines it should be warning Emacs users to not connect > these machines to the Internet. Well, my main development machine still runs XP, so for now this is a real necessity ;-)