Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Vir Campestris Newsgroups: comp.lang.c Subject: Re: constexpr keyword is unnecessary Date: Sat, 26 Oct 2024 15:07:05 +0100 Organization: A noiseless patient Spider Lines: 13 Message-ID: References: <877ca5q84u.fsf@nosuchdomain.example.com> <87y12jpxvl.fsf@nosuchdomain.example.com> <87plnvpgb9.fsf@nosuchdomain.example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Sat, 26 Oct 2024 16:07:05 +0200 (CEST) Injection-Info: dont-email.me; posting-host="1a34abd57199070a12913a6a127db11a"; logging-data="3944075"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+/o1vgbOEF+xXdRbYk7TZpUKdtoMH9p9A=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:Lo90YW6+3/zbsmGLGMOGIHEIxCU= In-Reply-To: Content-Language: en-GB Bytes: 1940 On 22/10/2024 13:48, Thiago Adams wrote: > > I think a more generic feature would be to have a standard way of > promoting selected warnings to errors. This would avoid stacking > features with small differences, such as treating constexpr as a special > case compared to other constant expressions in C. I have in the past had coding standards that require you to fix all warnings. After all, sometimes they do matter. IIRC we had a compiler that had a "treat warnings as errors" parameter. Andy