From: Alejandro Colomar <alx.manpages@gmail.com>
To: Alexander Monakov <amonakov@ispras.ru>
Cc: gcc@gcc.gnu.org, Andrew Clayton <andrew@digital-domain.net>
Subject: Re: -minstd: Require a minimum std version, without being specific
Date: Wed, 21 Dec 2022 20:08:07 +0100 [thread overview]
Message-ID: <cbd644ba-df35-bdac-1ebc-35ecee8b48d8@gmail.com> (raw)
In-Reply-To: <5fdb5cab-c35e-567e-5f7f-e46d4ee572a5@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1051 bytes --]
On 12/21/22 19:53, Alejandro Colomar wrote:
> Hi Alexander,
>
> On 12/21/22 19:51, Alexander Monakov wrote:
>>
>>
>> On Wed, 21 Dec 2022, Alejandro Colomar via Gcc wrote:
>>
>>> Hi,
>>>
>>> I've long had this wish: an option similar to -std, but which would not
>>> specify the standard. Rather, mark a requirement that the standard be at
>>> least a version.
>>>
>>> This would be especially useful for libraries, which might for example require
>>> C99 or C11 to work. They would be able to specify -minstd=c11 in their pc(5)
>>> file (for use with pkgconf(1)).
>>
>> There's already a standard, portable way to check:
>>
>> #if __STDC_VERSION__ < 201710
>> #error C17 required
>> #endif
>
> Hmm, not my favourite to stick that in every public header file, but yes, it's
> portable.
But yes, I could provide a <project/__compiler.h> "hidden" header that does all
this stuff, then include it everywhere. :)
>
> Thanks,
>
> Alex
>
>>
>> Alexander
>
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-21 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 18:33 Alejandro Colomar
2022-12-21 18:51 ` Alexander Monakov
2022-12-21 18:53 ` Alejandro Colomar
2022-12-21 19:08 ` Alejandro Colomar [this message]
2022-12-21 19:14 ` Jonathan Wakely
2022-12-21 19:12 ` Alexander Monakov
2022-12-21 19:15 ` Alejandro Colomar
2022-12-22 2:42 ` Ben Boeckel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cbd644ba-df35-bdac-1ebc-35ecee8b48d8@gmail.com \
--to=alx.manpages@gmail.com \
--cc=amonakov@ispras.ru \
--cc=andrew@digital-domain.net \
--cc=gcc@gcc.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.
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).