summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWolfgang Laun <Wolfgang.Laun@alcatel.at>2001-11-02 20:43:07 +0100
committerAbhijit Menon-Sen <ams@wiw.org>2001-11-02 16:47:43 +0000
commit3d555cb8c04bfcf8315c3f7c616b505041697522 (patch)
tree543f22bb5fc99b07b41ca24899641b7912e30441
parent7126c819b6c1cc54880a4a79a8f163e42699e1bb (diff)
downloadperl-3d555cb8c04bfcf8315c3f7c616b505041697522.tar.gz
Re: [PATCH] the the double double word word fix fix
Message-Id: <3BE2E93B.627C198E@alcatel.at> p4raw-id: //depot/perl@12815
-rw-r--r--pod/perldebug.pod12
1 files changed, 6 insertions, 6 deletions
diff --git a/pod/perldebug.pod b/pod/perldebug.pod
index 6232925581..2133fcf28e 100644
--- a/pod/perldebug.pod
+++ b/pod/perldebug.pod
@@ -921,12 +921,12 @@ interpret the information in that profile.
=head1 Debugging regular expressions
-C<use re 'debug'> enables you to see the gory details of how the
-Perl regular expression engine works. In order to understand this
-typically voluminous output, one must not only have some idea about
-about how regular expression matching works in general, but also
-know how Perl's regular expressions are internally compiled into
-an automaton. These matters are explored in some detail in
+C<use re 'debug'> enables you to see the gory details of how the Perl
+regular expression engine works. In order to understand this typically
+voluminous output, one must not only have some idea about how regular
+expression matching works in general, but also know how Perl's regular
+expressions are internally compiled into an automaton. These matters
+are explored in some detail in
L<perldebguts/"Debugging regular expressions">.
=head1 Debugging memory usage