Date: Sun, 09 Mar 2003 17:56:05 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: rich AT phekda DOT freeserve DOT co DOT uk Message-Id: <968-Sun09Mar2003175604+0200-eliz@elta.co.il> X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 CC: dj AT delorie DOT com, djgpp-workers AT delorie DOT com In-reply-to: <3E6B2DB0.D315AA68@phekda.freeserve.co.uk> (message from Richard Dawe on Sun, 09 Mar 2003 12:04:00 +0000) Subject: Re: New POSIX: pwrite, revision 2 [PATCH] References: <200303090033 DOT h290XfN11047 AT envy DOT delorie DOT com> <8632-Sun09Mar2003061943+0200-eliz AT elta DOT co DOT il> <3E6B2DB0 DOT D315AA68 AT phekda DOT freeserve DOT co DOT uk> Reply-To: Eli Zaretskii Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Sun, 09 Mar 2003 12:04:00 +0000 > From: Richard Dawe > > > > Yes, I agree: we should fail the function for character devices. > > Why should it fail for character devices? > > If I've understood the draft of new POSIX correctly, pwrite is allowed on > devices that do not support seeks. From the section describing write on the > write & pwrite page, it says: > > "On a file not capable of seeking, writing shall always take place starting at > the current position. The value of a file offset associated with such a device > is undefined." > > It does not say in the pwrite section that pwrite is not allowed on devices > that do not support seeks. In that case, I don't think we should fail the function at all. Sorry for not reading the standard before reviewing your code.