summaryrefslogtreecommitdiff
path: root/pod/perlre.pod
diff options
context:
space:
mode:
authorSteven Schubiger <schubiger@cpan.org>2005-10-31 23:48:27 +0100
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2005-11-10 10:52:51 +0000
commit4358a253560c226dd674c77f83b913c071c4fa25 (patch)
treed5881aefffcd9b943217161889e849dfb97df0ec /pod/perlre.pod
parent42d1cefd9a529012253aff0d502edf7a4f6a6ac3 (diff)
downloadperl-4358a253560c226dd674c77f83b913c071c4fa25.tar.gz
remove whitespace preceding semicolon in docs
Message-ID: <20051031214827.GH24416@accognoscere.homeunix.org> p4raw-id: //depot/perl@26073
Diffstat (limited to 'pod/perlre.pod')
-rw-r--r--pod/perlre.pod16
1 files changed, 8 insertions, 8 deletions
diff --git a/pod/perlre.pod b/pod/perlre.pod
index 23a7b0fa71..f24e97157b 100644
--- a/pod/perlre.pod
+++ b/pod/perlre.pod
@@ -960,14 +960,14 @@ But that isn't going to match; at least, not the way you're hoping. It
claims that there is no 123 in the string. Here's a clearer picture of
why that pattern matches, contrary to popular expectations:
- $x = 'ABC123' ;
- $y = 'ABC445' ;
+ $x = 'ABC123';
+ $y = 'ABC445';
- print "1: got $1\n" if $x =~ /^(ABC)(?!123)/ ;
- print "2: got $1\n" if $y =~ /^(ABC)(?!123)/ ;
+ print "1: got $1\n" if $x =~ /^(ABC)(?!123)/;
+ print "2: got $1\n" if $y =~ /^(ABC)(?!123)/;
- print "3: got $1\n" if $x =~ /^(\D*)(?!123)/ ;
- print "4: got $1\n" if $y =~ /^(\D*)(?!123)/ ;
+ print "3: got $1\n" if $x =~ /^(\D*)(?!123)/;
+ print "4: got $1\n" if $y =~ /^(\D*)(?!123)/;
This prints
@@ -1002,8 +1002,8 @@ are zero-width expressions--they only look, but don't consume any
of the string in their match. So rewriting this way produces what
you'd expect; that is, case 5 will fail, but case 6 succeeds:
- print "5: got $1\n" if $x =~ /^(\D*)(?=\d)(?!123)/ ;
- print "6: got $1\n" if $y =~ /^(\D*)(?=\d)(?!123)/ ;
+ print "5: got $1\n" if $x =~ /^(\D*)(?=\d)(?!123)/;
+ print "6: got $1\n" if $y =~ /^(\D*)(?=\d)(?!123)/;
6: got ABC