summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorTony Cook <tony@develop-help.com>2012-12-09 13:27:12 +1100
committerTony Cook <tony@develop-help.com>2012-12-09 13:27:12 +1100
commitf1ee460bffff6beafd031a678da686e1e5ebf4bf (patch)
tree434453f26bcc6da639c33aa4a8bfa95f8b918d90 /pod
parent596a6cbd6bcaa8e6a414f466dc748513439de5da (diff)
downloadperl-f1ee460bffff6beafd031a678da686e1e5ebf4bf.tar.gz
remove the warning added for 5.16 and indicate the count is chars not bytes
Diffstat (limited to 'pod')
-rw-r--r--pod/perlvar.pod9
1 files changed, 1 insertions, 8 deletions
diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index 47b202aba4..998ea422d4 100644
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -1358,7 +1358,7 @@ referenced integer. So this:
open my $fh, "<", $myfile or die $!;
local $_ = <$fh>;
-will read a record of no more than 32768 bytes from $fh. If you're
+will read a record of no more than 32768 characters from $fh. 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
@@ -1370,13 +1370,6 @@ 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.
-If you perform a record read on a FILE with an encoding layer such as
-C<:encoding(latin1)> or C<:utf8>, you may get an invalid string as a
-result, may leave the FILE positioned between characters in the stream
-and may not be reading the number of bytes from the underlying file
-that you specified. This behaviour may change without warning in a
-future version of perl.
-
You cannot call C<input_record_separator()> on a handle, only as a
static method. See L<IO::Handle|IO::Handle>.