summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorNick Ing-Simmons <nik@tiuk.ti.com>2004-07-28 16:12:54 +0100
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2004-08-02 16:40:36 +0000
commit59c9df153f318eb57e9c2dabb5d780ea5b7073fa (patch)
treeb7eadc72b4cf39ee361430c92d1077d78e3e57c8 /pod
parent0a0461ad65b6f6c174c7a1cc1a803c2f3d17ac03 (diff)
downloadperl-59c9df153f318eb57e9c2dabb5d780ea5b7073fa.tar.gz
Enhance the caveat in the description of tell()
Subject: Re: [perl #30788] Error in documentation Message-Id: <20040728141254.3861.5@llama.ing-simmons.net> p4raw-id: //depot/perl@23184
Diffstat (limited to 'pod')
-rw-r--r--pod/perlfunc.pod8
1 files changed, 3 insertions, 5 deletions
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 8708313051..9d9d0a07ee 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -5964,11 +5964,9 @@ tell() on pipes, fifos, and sockets usually returns -1.
There is no C<systell> function. Use C<sysseek(FH, 0, 1)> for that.
-Do not use tell() on a filehandle that has been opened using
-sysopen(), use sysseek() for that as described above. Why? Because
-sysopen() creates unbuffered, "raw", filehandles, while open() creates
-buffered filehandles. sysseek() make sense only on the first kind,
-tell() only makes sense on the second kind.
+Do not use tell() (or other buffered I/O operations) on a file handle
+that has been manipulated by sysread(), syswrite() or sysseek().
+Those functions ignore the buffering, while tell() does not.
=item telldir DIRHANDLE