From: Gisle Aas <gisle@aas.no>
Date: Mon, 4 Aug 2003 13:25:28 +0000 (-0700)
Subject: PerlIO_{read,write} return value doc patch
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=2c2cb4122eb316f028f8d8303287fd2a55536c62;p=p5sagit%2Fp5-mst-13.2.git

PerlIO_{read,write} return value doc patch
Message-ID: <lr4r0xuq4n.fsf@caliper.activestate.com>

p4raw-id: //depot/perl@20489
---

diff --git a/pod/perlapio.pod b/pod/perlapio.pod
index 98fc53d..10b8dc5 100644
--- a/pod/perlapio.pod
+++ b/pod/perlapio.pod
@@ -160,9 +160,14 @@ so it is (currently) legal to use C<printf(fmt,...)> in perl sources.
 
 =item B<PerlIO_read(f,buf,count)>, B<PerlIO_write(f,buf,count)>
 
-These correspond to fread() and fwrite(). Note that arguments are
-different, there is only one "count" and order has "file"
-first. Returns a byte count if successful (which may be zero or
+These correspond functionally to fread() and fwrite() but the
+arguments and return values are different.  The PerlIO_read() and
+PerlIO_write() signatures have been modeled on the more sane low level
+read() and write() functions instead: The "file" argument is passed
+first, there is only one "count", and the return value can distinguish
+between error and C<EOF>.
+
+Returns a byte count if successful (which may be zero or
 positive), returns negative value and sets C<errno> on error.
 Depending on implementation C<errno> may be C<EINTR> if operation was
 interrupted by a signal.