unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-28 9c222b9: Port to C compilers that lack size-0 arrays
Date: Fri, 3 Dec 2021 15:32:34 -0800	[thread overview]
Message-ID: <0974b643-eec7-9bc5-f166-6897dab2c4b0@cs.ucla.edu> (raw)
In-Reply-To: <83lf1178zy.fsf@gnu.org>

On 12/3/21 12:01, Eli Zaretskii wrote:

> Emacs still did compile on those platforms before your changes.

Actually the Emacs compile failed on both platforms, with many 
diagnostics, before my changes today. You're correct that the 
size-zero-array part of those changes was not needed to unbreak the two 
builds. Still, other builders may run into other less-commonly-used 
platforms that do not support this GNU C extension.


>> there's a reasonable chance it won't work on less-commonly-used
>> compilers and there's little point to taking that risk when the fix is
>> so simple.
> 
> That's okay, but such cleanup changes should be done on master, not on
> the release branch during a pretest.  The time for cleanups on the
> release branch has come and gone.  (And we don't support MSVC builds
> for a very long time now.)

Oh, I didn't know that Emacs builds with Microsoft compilers were no 
longer supported. Live and learn.... 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. Of course that'd be a 
low-priority cleanup.

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.



  reply	other threads:[~2021-12-03 23:32 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 [this message]
2021-12-04  7:35           ` Eli Zaretskii
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=0974b643-eec7-9bc5-f166-6897dab2c4b0@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --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).