diff options
| author | Jarkko Hietaniemi <jhi@iki.fi> | 2006-04-08 21:25:33 +0300 |
|---|---|---|
| committer | Nicholas Clark <nick@ccl4.org> | 2006-04-08 22:23:26 +0000 |
| commit | acbd132f67ad3746742c9e471142632e10bb9acc (patch) | |
| tree | 77aac9aa706b9e2c9b1f6df95dba1dcb84f4d37e /pod/perlvar.pod | |
| parent | a41cc44e8f73bd00013181fc01efa2336fcb557e (diff) | |
| download | perl-acbd132f67ad3746742c9e471142632e10bb9acc.tar.gz | |
sv.c, rs.t, perlvar.pod (Coverity finding: did you know what happens with $/=\0?)
Message-Id: <20060408152533.C4D5F6D08C@ugli.hut.fi>
(although I should add that this version of Coverity is actually
raising a false positive here, albeit something still interesting)
p4raw-id: //depot/perl@27744
Diffstat (limited to 'pod/perlvar.pod')
| -rw-r--r-- | pod/perlvar.pod | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/pod/perlvar.pod b/pod/perlvar.pod index 24db2956ae..e8a38cbf08 100644 --- a/pod/perlvar.pod +++ b/pod/perlvar.pod @@ -374,7 +374,8 @@ will read a record of no more than 32768 bytes from FILE. If you're not reading from a record-oriented file (or your OS doesn't have record-oriented files), then you'll likely get a full chunk of data with every read. If a record is larger than the record size you've -set, you'll get the record back in pieces. +set, you'll get the record back in pieces. Trying to set the record +size to zero or less will cause reading in the (rest of the) whole file. On VMS, record reads are done with the equivalent of C<sysread>, so it's best not to mix record and non-record reads on the same |