This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: howto restrict Warnings to non-system files?
- To: Markus Werle <markus at lufmech dot rwth-aachen dot de>
- Subject: Re: howto restrict Warnings to non-system files?
- From: Ingo Krabbe <ikrabbe at earthling dot net>
- Date: Fri, 29 Jun 2001 11:41:06 +0200 (CEST)
- cc: <gcc-bugs at gcc dot gnu dot org>
- Reply-To: Ingo Krabbe <i dot krabbe at dokom dot net>
On Thu, 28 Jun 2001, Markus Werle wrote:
>
> One little option (-Wnocomplain-on-own-headers) is missing ;-)
>
And thats the problem exactly. Whats about changing from one
stdc++ library or stl library to another. Ok thats not usefull anymore
since the libstdc++ works in our days. Nevertheless it doesn't really
belongs into the gcc tree. It is a subtree.
I would change your syntax into
-Wno-warn-on="/usr/include/g++-v3,myinclude.h". That option may come, but
it will be as uneasy to use as a simple grep command. You don't need to be
a unix-guru to know grep. If a begginner starts he should work with a IDE
first. Not even the IDE's know such filtering of error messages.
By the way it may be more usefull to really catch and drop out
when the programmer does common errors, like your c++-beginnig colleague
does them on using std::string. Your option you describe would only be
okay if the compiler user can define which headers should be viewed as
"OWN".
CU INGO