2011/3/31 Victor Stinner <victor.stin...@haypocalc.com>: > Le 01/04/2011 01:11, Benjamin Peterson a écrit : >> >> I'm rather sick of seeing this warnings on all compiles, so I propose >> we enable the -Wno-unused-results option. I judge that most of the >> cases where this occurs are error reporting functions, where not much >> with return code can be done. > > Can't we try to fix the warnings instead of turning them off? Or is it > possible to only turn off these warnings on a specific function?
It strikes me as excessively ugly. (see below) > > Modules/faulthandler.c emits a lot of such compiler warning, but there is > nothing interesting to do on write() error. I tried to turn off the warning > on an instruction using (void)write(...), but gcc doesn't understand that I > don't care of write() result here. You have actually have an assignment, like x = write(). -- Regards, Benjamin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
