Folks, It appears that a confused person has improperly interpreted documentation on the behavior of "\n" in perl on VMS. Here is a stab at correcting the situation. Please comment on it: does the change look ok? Would you suggest a re-wording? Are there any other misleading or incorrect portions of the perl documentation? Thanks very much for your comments. --- perl_9917/pod/perlfunc.pod_orig Tue May 1 16:16:18 2001 +++ perl_9917/pod/perlfunc.pod Tue May 1 16:16:10 2001 @@ -474,11 +474,11 @@ 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 +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 not necessarily the same across these platforms). +Consequently binmode() has no effect on these operating systems. In other +systems like OS/2, 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 End of Patch. Peter Prymmer
