Re: More C type errors by default for GCC 14

> From: Neal Gompa <[email protected]>
> Date: Wed, 10 May 2023 08:10:48 -0400
> Cc: [email protected], [email protected], [email protected], 
> 	[email protected], [email protected], [email protected], [email protected], 
> 	[email protected], [email protected]
> 
> On Wed, May 10, 2023 at 8:05 AM Eli Zaretskii <[email protected]> wrote:
> >
> > > From: Neal Gompa <[email protected]>
> > > Date: Wed, 10 May 2023 06:56:32 -0400
> > > Cc: Eric Gallager <[email protected]>, Jonathan Wakely <[email protected]>, [email protected],
> > >       David Edelsohn <[email protected]>, Eli Zaretskii <[email protected]>, Jakub Jelinek <[email protected]>,
> > >       Arsen Arsenović <[email protected]>, [email protected],
> > >       [email protected]
> > >
> > > Right, we've been going through a similar effort with C++ over the
> > > past decade. GCC incrementally becoming more strict on C++ has been an
> > > incredibly painful experience, and it eats away a ton of time that I
> > > would have spent dealing with other problems. Having one big event
> > > where the majority of changes to make the C compiler strict happen
> > > will honestly make it less painful, even if it doesn't seem like it at
> > > the moment.
> >
> > But not having such an event, ever, would be even less painful.
> 
> That's not going to happen.

Well, I hope it will.  Otherwise I wouldn't be partaking in this
discussion.