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

[Eric Blake]

On 08/30/2010 02:01 PM, Bruce Korb wrote:
> Meanwhile, gcc has added a new warning suppression option,
> --no-warn-unused-result (or very similar).

Yes, that's exactly Paul's suggestion - disable the gcc warning, and 
lose all the benefits it provides on other functions.

> I don't know so much about the uniqueness of fwrite, viz.
> why it is ignorable and fputc is not.

All the more reason to have an open bug against glibc and have Ulrich 
defend why fwrite is marked __wuc but not fputc (and hopefully, he is 
smart enough to remove __wuc from fwrite, rather than making things 
worse by adding it to fputc).

--
Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org