Change 18438 by rgs@rgs-home on 2003/01/04 15:24:22
Subject: Re: [PATCH] Tiny nits in perlre.pod
From: [EMAIL PROTECTED] (Andreas J. Koenig)
Date: Fri, 03 Jan 2003 00:57:15 +0100
Message-ID: <[EMAIL PROTECTED]>
Affected files ...
... //depot/perl/pod/perlre.pod#81 edit
Differences ...
==== //depot/perl/pod/perlre.pod#81 (text) ====
Index: perl/pod/perlre.pod
--- perl/pod/perlre.pod#80~18299~ Thu Dec 12 12:35:29 2002
+++ perl/pod/perlre.pod Sat Jan 4 07:24:22 2003
@@ -6,7 +6,7 @@
This page describes the syntax of regular expressions in Perl.
-if you haven't used regular expressions before, a quick-start
+If you haven't used regular expressions before, a quick-start
introduction is available in L<perlrequick>, and a longer tutorial
introduction is available in L<perlretut>.
@@ -564,7 +564,7 @@
B<WARNING>: This extended regular expression feature is considered
highly experimental, and may be changed or deleted without notice.
-This zero-width assertion evaluate any embedded Perl code. It
+This zero-width assertion evaluates any embedded Perl code. It
always succeeds, and its C<code> is not interpolated. Currently,
the rules to determine where the C<code> ends are somewhat convoluted.
@@ -627,7 +627,7 @@
you turn on the C<use re 'eval'>, though, it is no longer secure,
so you should only do so if you are also using taint checking.
Better yet, use the carefully constrained evaluation within a Safe
-module. See L<perlsec> for details about both these mechanisms.
+compartment. See L<perlsec> for details about both these mechanisms.
=item C<(??{ code })>
End of Patch.
