From: Joseph Myers <joseph@codesourcery.com>
To: Mike Stump <mikestump@comcast.net>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: Add -std=c18 etc. option aliases
Date: Fri, 17 Nov 2017 00:15:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1711162326220.14274@digraph.polyomino.org.uk> (raw)
In-Reply-To: <B3404324-61DA-4DF7-8208-E2C339570171@comcast.net>
On Thu, 16 Nov 2017, Mike Stump wrote:
> date on it. If there was no major release with c17, I would ditch the
> c17 spelling and just change it to c18 now. :-) I know, kinda sucks,
There is no evidence yet of anyone using the C18 name. So far, it's
consistently being referred to as C17 in development, even after the
timescale for the ballot / publication has become clear. But given the
possibility that some people might think of it as C18 based on the
publication date, being prepared with aliases seems useful.
The name -std=iso9899:2017 follows the precedent of -std=iso9899:199409 in
being based on the __STDC_VERSION__ value rather than the publication
date.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-11-16 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 23:10 Joseph Myers
2017-11-16 23:34 ` Mike Stump
2017-11-17 0:15 ` Joseph Myers [this message]
2017-11-17 7:47 ` Jakub Jelinek
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=alpine.DEB.2.20.1711162326220.14274@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
/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).