Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: David Brown <david.brown@hesbynett.no>
Newsgroups: comp.lang.c
Subject: Re: Baby X is bor nagain
Date: Sun, 30 Jun 2024 11:23:02 +0200
Organization: A noiseless patient Spider
Lines: 28
Message-ID: <v5r85n$f24s$1@dont-email.me>
References: <v494f9$von8$1@dont-email.me> <v5c86d$11ac7$1@dont-email.me>
 <JEheO.108086$ED9b.74955@fx11.iad> <v5cblg$11q0j$1@dont-email.me>
 <gEieO.108089$ED9b.25598@fx11.iad> <20240625113616.000075e0@yahoo.com>
 <mUzeO.141609$Cqra.55051@fx10.iad> <v5elql$1jmii$1@dont-email.me>
 <m3BeO.24907$Gurd.16179@fx34.iad> <v5empd$1jndv$2@dont-email.me>
 <v5eph4$1k6a9$1@dont-email.me> <87ed8jnbmf.fsf@bsb.me.uk>
 <v5jhls$2m7np$1@dont-email.me> <v5jm32$2nqvp$1@dont-email.me>
 <v5k3v2$2qllm$1@dont-email.me> <v5kfst$2svt3$1@dont-email.me>
 <v5kmlm$2u918$1@dont-email.me> <20240627201830.854@kylheku.com>
 <v5m2nl$39qob$3@dont-email.me> <20240628032211.403@kylheku.com>
 <v5p4rv$3u92q$1@dont-email.me> <86le2ndajg.fsf@linuxsc.com>
 <v5pbn7$75a$1@dont-email.me> <v5ph1a$1bkv$1@dont-email.me>
 <20240629214944.00002cc4@yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 30 Jun 2024 11:23:03 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="9899c24c591e6d78b08cc8b9e7f308eb";
	logging-data="493724"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19fFOp2XUxgy7h2b3i6sIqKqJopOCaNRzM="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.6.1
Cancel-Lock: sha1:b2C7LeYRCv/s9VXywEsZo14c8eE=
In-Reply-To: <20240629214944.00002cc4@yahoo.com>
Content-Language: en-GB
Bytes: 3162

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.