public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: giovannibajo@libero.it To: arthur.baldwin@gd-ais.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/10065: -pedantic has strange side effects; what is accepted in -std=c++98 Date: Fri, 16 May 2003 01:59:00 -0000 [thread overview] Message-ID: <20030516015955.11594.qmail@sources.redhat.com> (raw) Synopsis: -pedantic has strange side effects; what is accepted in -std=c++98 State-Changed-From-To: analyzed->closed State-Changed-By: bajo State-Changed-When: Fri May 16 01:59:54 2003 State-Changed-Why: Can't see a reason to keep this open. The problem with -pedantic converting errors to warning is already handled in c++/10032. Variable sized array are not supposed to be disabled with -ansi or -std=c++98 because they can't possibly conflict with well-formed ISO programs. The official way to disable extension is to use -pedantic, and -pedantic correctly reports a warning about it. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10065
next reply other threads:[~2003-05-16 1:59 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-16 1:59 giovannibajo [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-19 13:36 Giovanni Bajo 2003-03-22 4:22 bangerth
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=20030516015955.11594.qmail@sources.redhat.com \ --to=giovannibajo@libero.it \ --cc=arthur.baldwin@gd-ais.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).