diff options
author | Andy Lester <andy@petdance.com> | 2005-06-02 11:19:54 -0500 |
---|---|---|
committer | Rafael Garcia-Suarez <rgarciasuarez@gmail.com> | 2005-06-03 08:04:25 +0000 |
commit | b432a67249666bce4aa3385263660dc667d150d7 (patch) | |
tree | d7fccc07dbacb727f1e2d96499970be0b3682421 /pod/perlfaq6.pod | |
parent | 3a205795a9fa8c21e484e9a8efe6e9257c24bd1e (diff) | |
download | perl-b432a67249666bce4aa3385263660dc667d150d7.tar.gz |
Quotes in pod/*.pod
Message-ID: <20050602211954.GA22107@petdance.com>
p4raw-id: //depot/perl@24686
Diffstat (limited to 'pod/perlfaq6.pod')
-rw-r--r-- | pod/perlfaq6.pod | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/pod/perlfaq6.pod b/pod/perlfaq6.pod index 840f5de0ed..52ef09dfb0 100644 --- a/pod/perlfaq6.pod +++ b/pod/perlfaq6.pod @@ -8,9 +8,9 @@ This section is surprisingly small because the rest of the FAQ is littered with answers involving regular expressions. For example, decoding a URL and checking whether something is a number are handled with regular expressions, but those answers are found elsewhere in -this document (in L<perlfaq9>: ``How do I decode or create those %-encodings -on the web'' and L<perlfaq4>: ``How do I determine whether a scalar is -a number/whole/integer/float'', to be precise). +this document (in L<perlfaq9>: "How do I decode or create those %-encodings +on the web" and L<perlfaq4>: "How do I determine whether a scalar is +a number/whole/integer/float", to be precise). =head2 How can I hope to use regular expressions without creating illegible and unmaintainable code? @@ -509,8 +509,8 @@ regular expression: print "$count $line"; } -If you want these output in a sorted order, see L<perlfaq4>: ``How do I -sort a hash (optionally by value instead of key)?''. +If you want these output in a sorted order, see L<perlfaq4>: "How do I +sort a hash (optionally by value instead of key)?". =head2 How can I do approximate matching? @@ -794,7 +794,7 @@ looks like it is because "SG" is next to "XX", but there's no real Here are a few ways, all painful, to deal with it: - $martian =~ s/([A-Z][A-Z])/ $1 /g; # Make sure adjacent ``martian'' + $martian =~ s/([A-Z][A-Z])/ $1 /g; # Make sure adjacent "martian" # bytes are no longer adjacent. print "found GX!\n" if $martian =~ /GX/; |