delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2003/01/23/08:47:31

X-Sybari-Trust: eba97a37 9ffcebbb a34baef4 00000138
From: Martin Stromberg <eplmst AT epl DOT ericsson DOT se>
Message-Id: <200301231347.OAA06033@lws256.lu.erisoft.se>
Subject: Re: readv, writev [PATCH]
To: djgpp-workers AT delorie DOT com
Date: Thu, 23 Jan 2003 14:47:26 +0100 (MET)
In-Reply-To: <3E2FF0E4.3B0A5093@phekda.freeserve.co.uk> from "Richard Dawe" at Jan 23, 2003 01:40:52 PM
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

Richard said:
> Martin Stromberg wrote:
> > 
> > > Say you write the first part of the data, but then the write for the next
> > > part fails. What do you return? The call has failed, but you have written
> > > some
> > 
> > No. It succeeded in writing the first part. You return the value of as
> > many bytes you've written. (Just as write would do if it partially
                                                          ^^ "it" is write().
> > wrote something.)
> 
> If write partially writes something, it doesn't fail.
                                       ^^ Is "it" writev()?

The above sentence doesn't make sense, unless you misunderstood me.

Or I don't understand.

> If the second write fails, how do you know how much data it has written? I

Talking about write(): the return value if > 0. 0 otherwise.


Right,

							MartinS

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019