This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/11474] -Wreturn-type should default to on when compiling C++
- From: "gdr at integrable-solutions dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Jul 2003 14:54:43 -0000
- Subject: [Bug c++/11474] -Wreturn-type should default to on when compiling C++
- References: <20030709142428.11474.lloyd@randombit.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
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 gdr at integrable-solutions dot net 2003-07-14 14:54 -------
Subject: Re: -Wreturn-type should default to on when compiling C++
"bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> writes:
| What's wrong with asking people to please compile their code with -W -Wall?
In some circumstances, there are not practical.
I do not have strong feelings about warning by default.
| There are good reasons for most of the warning flags we have,
there are reasons we have flags. That they are "good" depends on your
definition of "good", and is certainly a matter of debate. The issue
is whether the warning should be on by default or not.
The same arguments you're making can be used for having the warning on
by default and telling people to use the -Wno- corresponding flags.
As you can see, the line you're reasoning cannot be determining.
| 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.
But it just does that by deciding which flags to turn off by default!
-- Gaby