From 7476a79c8db21237e6b6bcf579243fdfc880f8b9 Mon Sep 17 00:00:00 2001 From: Tony Cook Date: Sun, 18 Mar 2012 10:26:22 +1100 Subject: [rt #79960] document how broken $/ = \N is for unicode streams It's kind of late in the release process to change how $/ = \N works for unicode streams, briefly document how broken it is and let the user know it may change. --- pod/perlvar.pod | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/pod/perlvar.pod b/pod/perlvar.pod index 72968f1b80..ea1f601a80 100644 --- a/pod/perlvar.pod +++ b/pod/perlvar.pod @@ -1348,6 +1348,13 @@ want to read in record mode is probably unusable in line mode.) Non-VMS systems do normal I/O, so it's safe to mix record and non-record reads of a file. +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. + See also L. Also see L. Mnemonic: / delimits line boundaries when quoting poetry. -- cgit v1.2.1