From: Jarkko Hietaniemi <jhi@iki.fi>
Date: Mon, 2 Oct 2006 12:58:18 +0000 (+0300)
Subject: perldiag.pod: followup on the PerlIO::scalar patch
X-Git-Tag: accepted/trunk/20130322.191538~16963
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f5a7294f1dd651fb00c000797104b15457a93401;p=platform%2Fupstream%2Fperl.git

perldiag.pod: followup on the PerlIO::scalar patch
Message-ID: <4520E2BA.1000309@iki.fi>

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

diff --git a/pod/perldiag.pod b/pod/perldiag.pod
index d55ba22..ac67f15 100644
--- a/pod/perldiag.pod
+++ b/pod/perldiag.pod
@@ -2766,8 +2766,11 @@ which is odd, because hashes come in key/value pairs.
 
 (F, W layer) You tried to do a read/write/send/recv/seek operation
 with an offset pointing outside the buffer.  This is difficult to
-imagine.  The sole exception to this is that C<sysread()>ing past the
-buffer will extend the buffer and zero pad the new area.
+imagine.  The sole exceptions to this are that zero padding will
+take place when going past the end of the string when either
+C<sysread()>ing a file, or when seeking past the end of a scalar opened
+of I/O (in anticipation of future reads and to imitate the behaviour with
+real files).
 
 =item %s() on unopened %s