From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-28 9c222b9: Port to C compilers that lack size-0 arrays
Date: Sat, 04 Dec 2021 09:35:37 +0200 [thread overview]
Message-ID: <83ee6s7rg6.fsf@gnu.org> (raw)
In-Reply-To: <0974b643-eec7-9bc5-f166-6897dab2c4b0@cs.ucla.edu> (message from Paul Eggert on Fri, 3 Dec 2021 15:32:34 -0800)
> Date: Fri, 3 Dec 2021 15:32:34 -0800
> Cc: emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
>
> Oh, I didn't know that Emacs builds with Microsoft compilers were no
> longer supported. Live and learn....
We only support GCC and GNU Binutils for building Emacs on MS-Windows.
(And the MS-DOS build never supported anything else.)
> I suppose at some point any remaining references to MSVC could be
> removed from the Emacs source, if only to prevent further confusion
> in this area.
Yes.
> Anyway, the size-zero-array patch wasn't intended to be a mere cleanup
> change; it was a fix to avoid a portability regression in Emacs 28 with
> respect to this Standard C constraint. But if you'd rather move the
> patch to the master branch, feel free; or let me know and I'll do it.
Let's see if it actually causes some trouble on some system. If it
does, I will ask you to revert it on the release branch.
But in the future, please ask first.
next prev parent reply other threads:[~2021-12-04 7:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 8:16 emacs-28 9c222b9: Port to C compilers that lack size-0 arrays Eli Zaretskii
2021-12-03 16:46 ` Paul Eggert
2021-12-03 18:29 ` Eli Zaretskii
2021-12-03 19:42 ` Paul Eggert
2021-12-03 20:01 ` Eli Zaretskii
2021-12-03 23:32 ` Paul Eggert
2021-12-04 7:35 ` Eli Zaretskii [this message]
2021-12-04 10:47 ` Stefan Kangas
2021-12-04 11:24 ` Po Lu
2021-12-04 0:37 ` Po Lu
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=83ee6s7rg6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--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).