diff options
| author | Yves Orton <demerphq@gmail.com> | 2022-07-31 13:51:36 +0200 |
|---|---|---|
| committer | Yves Orton <demerphq@gmail.com> | 2022-08-03 11:07:09 +0200 |
| commit | 182f0ba91d539c8b2bea45168fd6e72f9f0073bd (patch) | |
| tree | cb19b24714d0519972231ede070dcbc14e66cf2a /pod/perlreguts.pod | |
| parent | 1db310d0443729d6e2d04e8cb339e9b79089b2ad (diff) | |
| download | perl-182f0ba91d539c8b2bea45168fd6e72f9f0073bd.tar.gz | |
regex engine - improved comments explaining REGNODE_AFTER()
This rewrites one comment to include more explanation of the difference
between Perl_regnext() and REGNODE_AFTER().
Diffstat (limited to 'pod/perlreguts.pod')
| -rw-r--r-- | pod/perlreguts.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlreguts.pod b/pod/perlreguts.pod index 3b73d14355..890bc68372 100644 --- a/pod/perlreguts.pod +++ b/pod/perlreguts.pod @@ -214,7 +214,7 @@ and equivalents for reading and setting the arguments; and C<STR_LEN()>, C<STRING()> and C<OPERAND()> for manipulating strings and regop bearing types. -=head3 What regop is next? +=head3 What regnode is next? There are two distinct concepts of "next regnode" in the regex engine, and it is important to keep them distinct in your thinking as they |