summaryrefslogtreecommitdiff
path: root/pod/perlvar.pod
diff options
context:
space:
mode:
authorKarl Williamson <public@khwilliamson.com>2012-12-11 16:51:59 -0700
committerKarl Williamson <public@khwilliamson.com>2012-12-11 18:10:18 -0700
commit3d24912184050c3b750afa33180de19735f6b960 (patch)
tree5db30930889db05a144b544448435c9010968f4f /pod/perlvar.pod
parent4b1e7f06143ab88e9b000eed23ae71e75b7c24b8 (diff)
downloadperl-3d24912184050c3b750afa33180de19735f6b960.tar.gz
perlvar.pod: Slight clarification, typo
Diffstat (limited to 'pod/perlvar.pod')
-rw-r--r--pod/perlvar.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index 998ea422d4..5b9b056eeb 100644
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -1352,7 +1352,7 @@ be better for something. :-)
Setting C<$/> to a reference to an integer, scalar containing an
integer, or scalar that's convertible to an integer will attempt to
read records instead of lines, with the maximum record size being the
-referenced integer. So this:
+referenced integer number of characters. So this:
local $/ = \32768; # or \"32768", or \$var_containing_32768
open my $fh, "<", $myfile or die $!;
@@ -1366,7 +1366,7 @@ 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 only, record reads bypass PerlIO layers and any associated
-buffering,so you must not mix record and non-record reads on the
+buffering, so you must not mix record and non-record reads on the
same filehandle. Record mode mixes with line mode only when the
same buffering layer is in use for both modes.