/usr/local/perl/lib/site_perl/5.8.5/Perl/Critic/Policy/RegularExpressions/RequireBracesForMultiline.pm |
Perl::Critic::Policy::RegularExpressions::RequireBracesForMultiline
Long regular expressions are hard to read. A good practice is to use
the x
modifier and break the regex into multiple lines with
comments explaining the parts. But, with the usual //
delimiters,
the beginning and end can be hard to match, especially in a s///
regexp. Instead, try using {}
characters to delimit your
expressions.
Compare these:
s/ <a \s+ href="([^"]+)"> (.*?) </a> /link=$1, text=$2/xms;
vs.
s{ <a \s+ href="([^"]+)"> (.*?) </a> } {link=$1, text=$2}xms;
Is that an improvement? Marginally, but yes. The curly braces lead the eye better.
Initial development of this policy was supported by a grant from the Perl Foundation.
Chris Dolan <cdolan@cpan.org>
Copyright (c) 2007 Chris Dolan. Many rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license can be found in the LICENSE file included with this module
/usr/local/perl/lib/site_perl/5.8.5/Perl/Critic/Policy/RegularExpressions/RequireBracesForMultiline.pm |