public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: at@sources.redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, papadopo@sources.redhat.com Subject: Re: c++/9658: compiler accepts invalid code Date: Fri, 14 Feb 2003 20:58:00 -0000 [thread overview] Message-ID: <20030214205812.911.qmail@sources.redhat.com> (raw) Synopsis: compiler accepts invalid code State-Changed-From-To: open->closed State-Changed-By: bangerth State-Changed-When: Fri Feb 14 20:58:12 2003 State-Changed-Why: That's a gcc extension. If you use -ansi -pedantic, you'll get tmp/g> /home/bangerth/bin/gcc-3.2.2-pre/bin/c++ -ansi -pedantic -c x.cc x.cc: In function `int main()': x.cc:2: warning: ISO C++ forbids array dimensions with parenthesized type in new The new parser in 3.4 rejects it outright (i.e. the extension has been removed): tmp/g> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc x.cc: In function `int main()': x.cc:2: error: expected `,' or `;' Wolfgang http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9658
next reply other threads:[~2003-02-14 20:58 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-14 20:58 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-11 10:26 papadopo, at, shfj, cea, fr
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=20030214205812.911.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=at@sources.redhat.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=papadopo@sources.redhat.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: 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).