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
