bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: bruno@clisp.org
Cc: bug-gnulib@gnu.org, rogerdpack@gmail.com
Subject: Re: gettimeofday.c windows version?
Date: Sun, 11 Dec 2022 19:25:13 +0200	[thread overview]
Message-ID: <83fsdlua2u.fsf@gnu.org> (raw)
In-Reply-To: <83h6y1ubfj.fsf@gnu.org> (message from Eli Zaretskii on Sun, 11 Dec 2022 18:56:00 +0200)

> Date: Sun, 11 Dec 2022 18:56:00 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: bug-gnulib@gnu.org, rogerdpack@gmail.com
> 
> > As some point, I want to get rid of the initialize() function and assume
> > a new enough version of the OS.
> 
> When that happens, Emacs will not be able to use Gnulib's gettime.c
> module, sadly.     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I meant on Windows, of course.

Look, this is an old argument, and we've disagreed about it more than
once.  My point is that there's a difference between when you stop
_testing_ your code on some old platform, as opposed to when you
deliberately break the build for that platform.  You want to do the
latter; I'm saying do the former, and let people who use the old
platform, such as they exist, test it for you and report problems.

There's no "cruft" in the code we are talking about.  It's valid code,
it is simple, easily understood, and doesn't present any maintenance
burdens.  Why remove it?  Just because Microsoft decided to EOL those
old systems?  The GNU project is supposed to have its own set of
values and considerations about that.  For example, we could consider
the many installations of those old versions in Third World countries
as being important enough for not dropping those systems.  That's what
Emacs does, and I urge Gnulib to do the same.


  reply	other threads:[~2022-12-11 17:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-11  6:01 gettimeofday.c windows version? Roger Pack
2022-12-11  7:05 ` Roger Pack
2022-12-11 14:22 ` Bruno Haible
2022-12-11 15:09   ` Eli Zaretskii
2022-12-11 16:20     ` Bruno Haible
2022-12-11 16:56       ` Eli Zaretskii
2022-12-11 17:25         ` Eli Zaretskii [this message]
2022-12-11 18:25           ` Bruno Haible
2022-12-11 18:55             ` Eli Zaretskii
2022-12-12  7:17               ` Paul Eggert
2022-12-12 12:19                 ` Bruno Haible
2022-12-12 13:06                 ` Eli Zaretskii
2022-12-12 14:25                   ` Bruno Haible
2022-12-12 14:40                     ` Eli Zaretskii
2022-12-12 19:44                       ` Paul Eggert
2022-12-12 20:37                         ` Eli Zaretskii
2022-12-16 23:35                           ` Paul Eggert
2022-12-17  8:09                             ` Eli Zaretskii
2022-12-12 19:14                     ` Gisle Vanem
2022-12-23  8:38   ` Roger Pack
2022-12-23  8:46     ` Eli Zaretskii
2022-12-23 23:47     ` Paul Eggert
2022-12-24  6:46       ` Eli Zaretskii
2022-12-24  7:42         ` Paul Eggert
2022-12-24  8:34           ` Eli Zaretskii

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://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=83fsdlua2u.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=rogerdpack@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.
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).