turning off warning messages in the source code

Ciaran O'Riordan ciaran_o_riordan@hotmail.com
Sat Oct 5 06:57:00 GMT 2002


>Gokhan Kisacikoglu says:
>
>Do you know if there is any work in progress in terms of disabling
>certain compiler features from the source code, including the warnings?

I haven't heard it mentioned on the lists and it's not in the open
projects file.

After thinking about it I agree that this should be implemented, I
wonder if it would be easy.  there should be a ((no_warn)) attribute
for functions.  Errors would still be errors.  There have to be a
command line switch to forcibly override this too.

>label each with an id number, then it
>would be easier to turn these on/off

This would also be good but would take a lot more work to implement.

If you're stuck you could pipe the output of gcc to 'egrep -v'.  A bit
of a kludge but if it was in a Makefile or script you wouldn't
notice it.

If you're trying to block "unused variable `p'" warnings you could
give the variable the ((unused)) attribute.  That's the only GCC
solution I can think of.



_________________________________________________________________
Join the worldÂ’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com



More information about the Gcc-help mailing list