Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <021a01c24d15$40c48c70$6132bc3e@BABEL> From: "Conrad Scott" To: References: <00c501c2496e$39ae2720$6132bc3e AT BABEL> <1029976536 DOT 27825 DOT 46 DOT camel AT lifelesswks> <025401c24a0d$1c996380$6132bc3e AT BABEL> <1030060087 DOT 8462 DOT 14 DOT camel AT lifelesswks> <20020824191035 DOT GB27153 AT redhat DOT com> <018201c24d0b$aa2d26e0$6132bc3e AT BABEL> <20020826162921 DOT M5475 AT cygbert DOT vinschen DOT de> <01cc01c24d10$f3b499b0$6132bc3e AT BABEL> <20020826145939 DOT GB1626 AT redhat DOT com> Subject: Re: readv/writev Date: Mon, 26 Aug 2002 16:28:38 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 "Christopher Faylor" wrote: > > On Mon, Aug 26, 2002 at 03:57:51PM +0100, Conrad Scott wrote: > > > >So, I'll go and worry about something else instead :-) > > Yes, I think worrying about a couple of if statements in > fhandler_base::read is really not worth anyone's time. That's fair enough. My worries were more about how easy it was to extend the fhandler class, which I came across while pondering a readv/writev implementation, and that was more of a worry about code duplication than anything else. But it's academic right now. Cheers, // Conrad