summaryrefslogtreecommitdiff
path: root/pod/perlreguts.pod
diff options
context:
space:
mode:
authorRafael Garcia-Suarez <rgarciasuarez@gmail.com>2006-06-26 08:55:56 +0000
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2006-06-26 08:55:56 +0000
commite3950ac3c808dcb52f5815999e90a3e00a9f7159 (patch)
tree63b94cf04b693973795cb83bcb773e8db2b9b29d /pod/perlreguts.pod
parent0b390a8204ce53b7d71cfce2604bf3aa78e34f74 (diff)
downloadperl-e3950ac3c808dcb52f5815999e90a3e00a9f7159.tar.gz
More perlreguts nits by Dominic Dunlop,
plus fix a broken internal POD link p4raw-id: //depot/perl@28428
Diffstat (limited to 'pod/perlreguts.pod')
-rw-r--r--pod/perlreguts.pod9
1 files changed, 5 insertions, 4 deletions
diff --git a/pod/perlreguts.pod b/pod/perlreguts.pod
index 32da4256fa..fb7669ca18 100644
--- a/pod/perlreguts.pod
+++ b/pod/perlreguts.pod
@@ -34,7 +34,7 @@ code form and their internal form. In this document we will use the term
"pattern" when we speak of their textual, source code form, the term
"program" when we speak of their internal representation. These
correspond to the terms I<S-regex> and I<B-regex> that Mark Jason
-Dominus employs in his paper on "Rx" ([1] in L</references>).
+Dominus employs in his paper on "Rx" ([1] in L</REFERENCES>).
=head2 What is a regular expression engine?
@@ -669,9 +669,10 @@ a string. It returns an integer 1 for success and a 0 for failure.
It is basically a set-up wrapper around C<regmatch()>.
C<regmatch> is the main "recursive loop" of the interpreter. It is
-basically a giant switch statement that executes the regops based on
-their type. A few of the regops are implemented as subroutines but
-the bulk are inline code.
+basically a giant switch statement that implements a state machine, where
+the possible states are the regops themselves, plus a number of additional
+intermediate and failure states. A few of the states are implemented as
+subroutines but the bulk are inline code.
=head1 MISCELLANEOUS