public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/11474] -Wreturn-type should default to on when compiling C++ Date: Mon, 14 Jul 2003 14:40:00 -0000 [thread overview] Message-ID: <20030714144044.21145.qmail@sources.redhat.com> (raw) In-Reply-To: <20030709142428.11474.lloyd@randombit.net> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11474 ------- Additional Comments From bangerth at dealii dot org 2003-07-14 14:40 ------- What's wrong with asking people to please compile their code with -W -Wall? There are good reasons for most of the warning flags we have, so people should just learn to use warning flags. It's not gcc's task to _think_ for programmers unless they specifically ask for it. By the same argument, we also don't switch on optimizations by default, but ask people to do so explicitly on the command line. W.
next prev parent reply other threads:[~2003-07-14 14:40 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-09 14:24 [Bug c++/11474] New: " lloyd at randombit dot net 2003-07-09 14:39 ` [Bug c++/11474] " bangerth at dealii dot org 2003-07-13 7:40 ` gdr at integrable-solutions dot net 2003-07-13 7:41 ` gdr at integrable-solutions dot net 2003-07-13 8:22 ` zack at gcc dot gnu dot org 2003-07-13 16:39 ` lloyd at randombit dot net 2003-07-13 16:51 ` jsm at polyomino dot org dot uk 2003-07-14 14:40 ` bangerth at dealii dot org [this message] 2003-07-14 14:54 ` gdr at integrable-solutions dot net 2003-07-14 15:12 ` bangerth at dealii dot org [not found] <bug-11474-4@http.gcc.gnu.org/bugzilla/> 2020-04-26 9:43 ` redi at gcc dot gnu.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=20030714144044.21145.qmail@sources.redhat.com \ --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).