On Fri, 2011-06-10 at 14:47 +0100, Ben Hutchings wrote: > On Fri, 2011-06-10 at 15:08 +0200, Marc Lehmann wrote: > [...] > > Reading standards is notoriously difficult, I admit. The behaviour of read > > is specified to read the requested number of bytes, if possible. > > > > The standard gives an exception list where applications can deviate from > > the behaviour and read less. > [...] > > "Implementations may support additional errors not included in this > list, may generate errors included in this list under circumstances > other than those described here, or may contain extensions or > limitations that prevent some errors from occurring." This is not directly relevant to truncation of read/write, but I think it illustrates the general principle that POSIX does not claim to enumerate all I/O failure conditions (which would be a denial of reality). Ben. > Please fix your application and give up this argument. > > Ben. > -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison
Attachment:
signature.asc
Description: This is a digitally signed message part