From: Peter Prymmer Date: Wed, 2 May 2001 15:58:18 +0000 (-0700) Subject: fix some misinformation in perlfunc.pod X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=5e12dbfa1fc5fab9ffcdf3a398fa9f5c92327e0d;p=p5sagit%2Fp5-mst-13.2.git fix some misinformation in perlfunc.pod Message-ID: p4raw-id: //depot/perl@9968 --- diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index a7e6ef7..29e496f 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -474,17 +474,17 @@ representation matches the internal representation, but on some platforms the external representation of C<\n> is made up of more than one character. -Mac OS and all variants of Unix use a single character to end each line -in the external representation of text (even though that single -character is not necessarily the same across these platforms). -Consequently binmode() has no effect on these operating systems. In -other systems like VMS, MS-DOS and the various flavors of MS-Windows -your program sees a C<\n> as a simple C<\cJ>, but what's stored in text -files are the two characters C<\cM\cJ>. That means that, if you don't -use binmode() on these systems, C<\cM\cJ> sequences on disk will be -converted to C<\n> on input, and any C<\n> in your program will be -converted back to C<\cM\cJ> on output. This is what you want for text -files, but it can be disastrous for binary files. +Mac OS, all variants of Unix, and Stream_LF files on VMS use a single +character to end each line in the external representation of text (even +though that single character is CARRIAGE RETURN on Mac OS and LINE FEED +on Unix and most VMS files). Consequently binmode() has no effect on +these operating systems. In other systems like OS/2, DOS and the various +flavors of MS-Windows your program sees a C<\n> as a simple C<\cJ>, but +what's stored in text files are the two characters C<\cM\cJ>. That means +that, if you don't use binmode() on these systems, C<\cM\cJ> sequences on +disk will be converted to C<\n> on input, and any C<\n> in your program +will be converted back to C<\cM\cJ> on output. This is what you want for +text files, but it can be disastrous for binary files. Another consequence of using binmode() (on some systems) is that special end-of-file markers will be seen as part of the data stream. diff --git a/pod/perlport.pod b/pod/perlport.pod index deb0a38..fc96531 100644 --- a/pod/perlport.pod +++ b/pod/perlport.pod @@ -874,10 +874,11 @@ process on VMS, is a pure Perl module that can easily be installed on non-VMS platforms and can be helpful for conversions to and from RMS native formats. -What C<\n> represents depends on the type of file opened. It could -be C<\015>, C<\012>, C<\015\012>, or nothing. The VMS::Stdio module -provides access to the special fopen() requirements of files with unusual -attributes on VMS. +What C<\n> represents depends on the type of file opened. It usually +represents C<\012> but it could also be C<\015>, C<\012>, C<\015\012>, +C<\000>, C<\040>, or nothing depending on the file organiztion and +record format. The VMS::Stdio module provides access to the +special fopen() requirements of files with unusual attributes on VMS. TCP/IP stacks are optional on VMS, so socket routines might not be implemented. UDP sockets may not be supported.