Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

perl::critic::policy::regularexpressions::prohibitescapedmetacha(3pm) [debian man page]

Perl::Critic::Policy::RegularExpressions::ProhibitEscapeUseraContributPerl::Critic::Policy::RegularExpressions::ProhibitEscapedMetacharacters(3pm)

NAME

       Perl::Critic::Policy::RegularExpressions::ProhibitEscapedMetacharacters - Use character classes for literal meta-characters instead of
       escapes.

AFFILIATION

       This Policy is part of the core Perl::Critic distribution.

DESCRIPTION

       Ever heard of leaning toothpick syndrome?  That comes from writing regular expressions that match on characters that are significant in
       regular expressions.  For example, the expression to match four forward slashes looks like:

	   m//////;

       Well, this policy doesn't solve that problem (write it as "m{////}" instead!) but solves a related one.	As seen above, the escapes make
       the expression hard to parse visually.  One solution is to use character classes.  You see, inside of character classes, the only
       characters that are special are "", "]", "^" and "-", so you don't need to escape the others.  So instead of the following loose IPv4
       address matcher:

	   m/ d+ . d+ . d+ . d+ /x;

       You could write:

	   m/ d+ [.] d+ [.] d+ [.] d+ /x;

       which is certainly more readable, if less recognizable prior the publication of Perl Best Practices.  (Of course, you should really use
       Regexp::Common::net to match IPv4 addresses!)

       Specifically, this policy forbids backslashes immediately prior to the following characters:

	   { } ( ) . * + ? | #

       We make special exception for "$" because "/[$]/" turns into "/[5.008006/" for Perl 5.8.6.  We also make an exception for "^" because it
       has special meaning (negation) in a character class.  Finally, "[" and "]" are exempt, of course, because they are awkward to represent in
       character classes.

       Note that this policy does not forbid unnecessary escaping.  So go ahead and (pointlessly) escape "!" characters.

CONFIGURATION

       This Policy is not configurable except for the standard options.

BUGS

       Perl treats "m/[#]/x" in unexpected ways.  I think it's a bug in Perl itself, but am not 100% sure that I have not simply misunderstood...

       This part makes sense:

	   "#f" =~ m/[#]f/x;	 # match
	   "#f" =~ m/[#]a/x;	 # no match

       This doesn't:

	   $qr	= qr/f/;
	   "#f" =~ m/[#]$qr/x; # no match

       Neither does this:

	   print qr/[#]$qr/x;  # yields '(?x-ism:[#]$qr
				       )'

CREDITS

       Initial development of this policy was supported by a grant from the Perl Foundation.

AUTHOR

       Chris Dolan <cdolan@cpan.org>

COPYRIGHT

       Copyright (c) 2007-2011 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

perl v5.14.2							    20Perl::Critic::Policy::RegularExpressions::ProhibitEscapedMetacharacters(3pm)

Check Out this Related Man Page

Perl::Critic::Policy::RegularExpressions::ProhibitCapturUserhContributed)Perl::Critic::Policy::RegularExpressions::ProhibitCaptureWithoutTest(3pm)

NAME

       Perl::Critic::Policy::RegularExpressions::ProhibitCaptureWithoutTest - Capture variable used outside conditional.

AFFILIATION

       This Policy is part of the core Perl::Critic distribution.

DESCRIPTION

       If a regexp match fails, then any capture variables ($1, $2, ...) will be undefined.  Therefore it's important to check the return value of
       a match before using those variables.

       This policy checks that the previous regexp for which the capture variable is in-scope is either in a conditional or causes an exception or
       other control transfer (i.e. "next", "last", "redo", "return", or sometimes "goto") if the match fails.

       A "goto" is only accepted by this policy if it is a co-routine call (i.e.  "goto &foo") or a "goto LABEL" where the label does not fall
       between the "goto" and the capture variable in the scope of the "goto". A computed "goto" (i.e. something like "goto (qw{foo bar
       baz})[$i]") is not accepted by this policy because its target can not be statically determined.

       This policy does not check whether that conditional is actually testing a regexp result, nor does it check whether a regexp actually has a
       capture in it.  Those checks are too hard.

       This policy also does not check arbitrarily complex conditionals guarding regexp results, for pretty much the same reason.  Simple things
       like

	m/(foo)/ or die "No foo!";
	die "No foo!" unless m/(foo)/;

       will be handled, but something like

	m/(foo) or do {
	  ... lots of complicated calculations here ...
	  die "No foo!";
	};

       are beyond its scope.

CONFIGURATION

       By default, this policy considers "die", "croak", and "confess" to throw exceptions. If you have additional subroutines or methods that may
       be used in lieu of one of these, you can configure them in your perlcriticrc as follows:

	[RegularExpressions::ProhibitCaptureWithoutTest]
	exception_source = my_exception_generator

BUGS

       This policy does not recognize named capture variables. Yet.

AUTHOR

       Chris Dolan <cdolan@cpan.org>

COPYRIGHT

       Copyright (c) 2006-2011 Chris Dolan.

       This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.14.2							    2012-Perl::Critic::Policy::RegularExpressions::ProhibitCaptureWithoutTest(3pm)
Man Page