From: Tony Cook Date: Fri, 20 Oct 2000 07:29:15 +0000 (+1100) Subject: PATCH CR+LF should be "\cM\cJ" in perlop X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=2a380090627f0ffa242f982195676354d1a2db22;p=p5sagit%2Fp5-mst-13.2.git PATCH CR+LF should be "\cM\cJ" in perlop Message-ID: p4raw-id: //depot/perl@7373 --- diff --git a/pod/perlop.pod b/pod/perlop.pod index 32eaa3c..e97a25b 100644 --- a/pod/perlop.pod +++ b/pod/perlop.pod @@ -710,7 +710,7 @@ on a Mac, these are reversed, and on systems without line terminator, printing C<"\n"> may emit no actual data. In general, use C<"\n"> when you mean a "newline" for your system, but use the literal ASCII when you need an exact character. For example, most networking protocols expect -and prefer a CR+LF (C<"\012\015"> or C<"\cJ\cM">) for line terminators, +and prefer a CR+LF (C<"\015\012"> or C<"\cM\cJ">) for line terminators, and although they often accept just C<"\012">, they seldom tolerate just C<"\015">. If you get in the habit of using C<"\n"> for networking, you may be burned some day.