public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "U.Mutlu" <um@mutluit.com>
Cc: Jakub Jelinek <jakub@redhat.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [wwwdocs] C++03 missing on https://gcc.gnu.org/projects/cxx-status.html
Date: Thu, 15 Dec 2022 20:09:53 +0000	[thread overview]
Message-ID: <CAH6eHdS3m-VKGf=hiDUvNtzVHi-HfWnutbTpvg7+XWU0jNB7ew@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRGnE3mGumShYHchACaXb9bdCNz4yGYootYT+-TH=-y9A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]

On Thu, 15 Dec 2022, 20:04 Jonathan Wakely, <jwakely.gcc@gmail.com> wrote:

>
>
> On Thu, 15 Dec 2022, 19:50 U.Mutlu, <um@mutluit.com> wrote:
>
>> Jakub Jelinek wrote on 12/15/22 17:59:
>> > On Thu, Dec 15, 2022 at 05:53:19PM +0100, U.Mutlu wrote:
>> >> On this page all ISO C++ standards versions of gcc/g++ are listed,
>> except C++03:
>> >> https://gcc.gnu.org/projects/cxx-status.html
>> >>
>> >> This looks much like an error/omission b/c g++ has the options
>> -std=c++03
>> >> and -std=gnu++03
>> >
>> > C++03 isn't a separate standard version, just technical corrigendum
>> > and the page mentions it:
>> >
>> > C++98 Support in GCC
>> > GCC has full support for the 1998 C++ standard as modified by the 2003
>> > technical corrigendum
>> >
>> > -std=c++03 is an alias to -std=c++98 and -std=gnu++03 is an alias to
>> > -std=gnu++98 and the gcc manual explains that.
>> >
>> >       Jakub
>>
>>
>> Whatever, but they still could list it like the others and then give the
>> explanation you gave.
>> B/c otherwise it looks like as if the doc writer has forgotten one of the
>> historic steps...
>>
>
> I disagree. If you actually know what the -std=c++03 option means, you
> wouldn't think that. And it already says GCC had full support for C++ 1998
> *including the 2003 Technical Corrigendum*.
>
> The document doesn't need to be clear to people who have no idea what C++
> is, or what the gcc options mean, because that's not the audience it's
> intended for
>


We could add "The options -std=c++03 and -std=gnu++03 are equivalent to
-std=c++98 and -std=gnu++98, respectively." To the very end. That would not
be as misleading as adding a separate artificial listing for C++03.

  reply	other threads:[~2022-12-15 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 16:53 U.Mutlu
2022-12-15 16:59 ` Jakub Jelinek
2022-12-15 19:50   ` U.Mutlu
2022-12-15 20:04     ` Jonathan Wakely
2022-12-15 20:09       ` Jonathan Wakely [this message]
2022-12-19 11:09 ` Jonathan Wakely

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='CAH6eHdS3m-VKGf=hiDUvNtzVHi-HfWnutbTpvg7+XWU0jNB7ew@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=um@mutluit.com \
    /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).