summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorTony Cook <tony@develop-help.com>2000-10-20 18:29:15 +1100
committerJarkko Hietaniemi <jhi@iki.fi>2000-10-20 00:56:35 +0000
commit2a380090627f0ffa242f982195676354d1a2db22 (patch)
tree5c3df4d0369465af0f958dee8a77d7ba4585630b /pod
parent2f7c487ece3f6663073bba69dfb8f4a27b9524e7 (diff)
downloadperl-2a380090627f0ffa242f982195676354d1a2db22.tar.gz
PATCH CR+LF should be "\cM\cJ" in perlop
Message-ID: <Pine.LNX.4.10.10010200725530.12682-100000@develop-help.com> p4raw-id: //depot/perl@7373
Diffstat (limited to 'pod')
-rw-r--r--pod/perlop.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlop.pod b/pod/perlop.pod
index 32eaa3c330..e97a25bc9b 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.