public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lloyd at randombit dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/28368] -std=c89 doesn't warn about gcc's "?:" extension Date: Wed, 07 Mar 2007 14:48:00 -0000 [thread overview] Message-ID: <20070307144749.26997.qmail@sourceware.org> (raw) In-Reply-To: <bug-28368-838@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from lloyd at randombit dot net 2007-03-07 14:47 ------- This is also true for C++ unless -pedantic is specified (which is confusing since I thought -pedantic-errors was the default for C++, but apparently this changed at some point). Using '-Wall -Wextra -ansi -std=c++98' gives no warning. I'm not sure if it's really a bug, since the GCC docs make it pretty clear that -ansi et. al. are basically useless in terms of getting it to warn you about using extensions, but it is certainly unexpected. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28368
next prev parent reply other threads:[~2007-03-07 14:48 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-13 6:28 [Bug c/28368] New: gcc-bugzilla at gcc dot gnu dot org 2007-03-07 14:48 ` lloyd at randombit dot net [this message] 2007-03-07 17:57 ` [Bug c/28368] -std=c89 doesn't warn about gcc's "?:" extension manu at gcc dot gnu dot org 2007-03-07 18:04 ` joseph at codesourcery dot com 2007-03-07 18:11 ` manu at gcc dot gnu dot org 2007-03-07 21:06 ` joseph at codesourcery dot com 2007-03-08 15:52 ` manu at gcc dot gnu dot org 2008-01-18 12:46 ` manu at gcc dot gnu dot org 2008-02-16 16:30 ` manu at gcc dot gnu dot org 2008-02-16 18:16 ` manu at gcc dot gnu dot org 2008-02-16 18:21 ` manu at gcc dot gnu dot org
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=20070307144749.26997.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).