Re: Baby X is bor nagain

On 29/06/2024 20:49, Michael S wrote:

On Sat, 29 Jun 2024 19:42:01 +0200
David Brown <david.brown@hesbynett.no> wrote:

>
gcc, however, is restricted and limited by its past - the developers
do not lightly make changes that will result in compilation failures
of code that previously compiled fine and had been tested to run
correctly. Such changes - as made for gcc 14 - are only done after
long discussion and long testing with existing code bases.
>

 Default input dialect of C language was changed (it seems, to gnu17)
before gcc14. May be, in gcc12.
BTW, finding out what dialect is a defaul is less than trivial. If Bart
calls it "jump through a number of hoops" he would at least correct,
but more like understating his case.
 

That would be the wrong hoops to jump through.  Don't use the default standard unless you are writing a little hello world program and don't care about the choice of standard - /specify/ the standard you want. And that one is a very, very simple jump.
But as Keith said, this change was not about C standards.  It was about gcc developers changing the balance between being stricter about defaults to reduce future programmers' mistakes, and being lax about defaults to allow older and poorer code to compile without error messages.