[Vm-dev] [Fix] Avoid recent gcc error messages about unused
write(2) return value
Bert Freudenberg
bert at freudenbergs.de
Fri Jan 30 14:42:36 UTC 2009
On 30.01.2009, at 14:22, Philippe Marschall wrote:
>
> 2009/1/30 Damien Cassou <damien.cassou at gmail.com>:
>>
>> See attachment.
>>
>> [Fix] Avoid recent gcc error messages about unused write(2) return
>> value
>
> There is a reason why GCC forces you to check the return value.
This is actually not GCC's fault, but newer header files declare
write() with the warn_unused_result attribute to enforce that check.
- Bert -
More information about the Vm-dev
mailing list