This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: How to ignore Wall errors for a portion of code
- From: Brian Dessent <brian at dessent dot net>
- To: MSX to GCC <gcc-help at gcc dot gnu dot org>
- Date: Mon, 15 Jan 2007 06:51:25 -0800
- Subject: Re: How to ignore Wall errors for a portion of code
- References: <C1D0EBF1.1B4EB%eljay@adobe.com>
- Reply-to: gcc-help at gcc dot gnu dot org
John Love-Jensen wrote:
> For Quick-&-Dirty alternative, you can post-process the GCC output with
> Perl, Python, sed, awk, or whatever other preferred regex capable scripting
> engine you prefer, and filter out the undesired messages.
Or better, stop using #include for non-header files and compile them
separately so that you can control the warning flags used for each.
(That doesn't really help if the code is templates which much be
included, but the poster didn't state that's what they were doing and
even then they should be put in a header file and not included as a .c
file.)
Brian