Re: failure to build due to ignoring fwrite() result

[Bruce Korb]

On Mon, Aug 30, 2010 at 1:57 PM, Jim Meyering <address@hidden> wrote:
> That said, if there is a way to tell gcc to ignore
> a particular otherwise-offending WUR warning without
> cluttering up our code, I'd be interested.

That a simple cast to void says that part of the issue is a gcc bug.
Anyplace where a compiler presumes to know more than the programmer
is a bug.

However, given what GCC does with "wur", the tagging of fwrite() is a bug.
This is a two-fer.  ("two for one", for those not familiar with the idiom.)