perl::critic::policy::modules::requirenomatchvarswithuseenglish(3) [centos man page]

Perl::Critic::Policy::Modules::RequireNoMatchVarsWithUseUseriContributed Perl DoPerl::Critic::Policy::Modules::RequireNoMatchVarsWithUseEnglish(3)

NAME

       Perl::Critic::Policy::Modules::RequireNoMatchVarsWithUseEnglish - "use English" must be passed a "-no_match_vars" argument.

AFFILIATION

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

DESCRIPTION

       Due to unfortunate history, if you use the English module but don't pass in a "-no_match_vars" argument, all regular expressions in the
       entire program, not merely the module in question, suffer a significant performance penalty, even if you only import a subset of the
       variables.

	   use English; 			     # not ok
	   use English '-no_match_vars';	     # ok
	   use English qw< $ERRNO -no_match_vars >;  # ok
	   use English qw($OS_ERROR);		     # not ok

       In the last example above, while the match variables aren't loaded into your namespace, they are still created in the "English" namespace
       and you still pay the cost.

CONFIGURATION

       This Policy is not configurable except for the standard options.

AUTHOR

       Elliot Shank "<perl@galumph.com>"

COPYRIGHT

       Copyright (c) 2008-2011 Elliot Shank.

       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.16.3							    2014-06-09	Perl::Critic::Policy::Modules::RequireNoMatchVarsWithUseEnglish(3)

Perl::Critic::Policy::Variables::ProhibitLocalVars(3)	User Contributed Perl Documentation  Perl::Critic::Policy::Variables::ProhibitLocalVars(3)

NAME

       Perl::Critic::Policy::Variables::ProhibitLocalVars - Use "my" instead of "local", except when you have to.

AFFILIATION

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

DESCRIPTION

       Since Perl 5, there are very few reasons to declare "local" variables.  The most common exceptions are Perl's magical global variables.	If
       you do need to modify one of those global variables, you should localize it first.  You should also use the English module to give those
       variables more meaningful names.

	   local $foo;	 #not ok
	   my $foo;	 #ok

	   use English qw(-no_match_vars);
	   local $INPUT_RECORD_SEPARATOR    #ok
	   local $RS			    #ok
	   local $/;			    #not ok

CONFIGURATION

       This Policy is not configurable except for the standard options.

NOTES

       If an external module uses package variables as its interface, then using "local" is actually a pretty sensible thing to do.  So
       Perl::Critic will not complain if you "local"-ize variables with a fully qualified name such as $Some::Package::foo.  However, if you're in
       a position to dictate the module's interface, I strongly suggest using accessor methods instead.

SEE ALSO

       Perl::Critic::Policy::Variables::ProhibitPunctuationVars

AUTHOR

       Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>

COPYRIGHT

       Copyright (c) 2005-2011 Imaginative Software Systems.  All 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.16.3							    2014-06-09		     Perl::Critic::Policy::Variables::ProhibitLocalVars(3)