Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

perl::critic::policy::variables::requirelexicalloopiterators(3) [centos man page]

Perl::Critic::Policy::Variables::RequireLexicalLoopIteraUser(Contributed Perl DocumPerl::Critic::Policy::Variables::RequireLexicalLoopIterators(3)

NAME
Perl::Critic::Policy::Variables::RequireLexicalLoopIterators - Write "for my $element (@list) {...}" instead of "for $element (@list) {...}". AFFILIATION
This Policy is part of the core Perl::Critic distribution. DESCRIPTION
This policy asks you to use "my"-style lexical loop iterator variables: foreach my $zed (...) { ... } Unless you use "my", "for"/"foreach" loops use a global variable with its value "local" to the block. In other words, foreach $zed (...) { ... } is more-or-less equivalent to { local $zed foreach $zed (...) { ... } } This may not seem like a big deal until you see code like my $bicycle; for $bicycle (@things_attached_to_the_bike_rack) { if ( $bicycle->is_red() and $bicycle->has_baseball_card_in_spokes() and $bicycle->has_bent_kickstand() ) { $bicycle->remove_lock(); last; } } if ( $bicycle and $bicycle->is_unlocked() ) { ride_home($bicycle); } which is not going to allow you to arrive in time for dinner with your family because the $bicycle outside the loop is not changed by the loop. You may have unlocked your bicycle, but you can't remember which one it was. Lexical loop variables were introduced in Perl 5.004. This policy does not report violations on code which explicitly specifies an earlier version of Perl (e.g. "require 5.002;"). CONFIGURATION
This Policy is not configurable except for the standard options. SEE ALSO
"Foreach Loops" in perlsyn "my() in Control Structures" in perl5004delta 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::RequireLexicalLoopIterators(3)

Check Out this Related Man Page

Perl::Critic::Policy::TestingAndDebugging::ProhibitNoWarUsersContributed Perl DocuPerl::Critic::Policy::TestingAndDebugging::ProhibitNoWarnings(3)

NAME
Perl::Critic::Policy::TestingAndDebugging::ProhibitNoWarnings - Prohibit various flavors of "no warnings". AFFILIATION
This Policy is part of the core Perl::Critic distribution. DESCRIPTION
There are good reasons for disabling certain kinds of warnings. But if you were wise enough to "use warnings" in the first place, then it doesn't make sense to disable them completely. By default, any "no warnings" statement will violate this policy. However, you can configure this Policy to allow certain types of warnings to be disabled (See "CONFIGURATION"). A bare "no warnings" statement will always raise a violation. CONFIGURATION
The permitted warning types can be configured via the "allow" option. The value is a list of whitespace-delimited warning types that you want to be able to disable. See perllexwarn for a list of possible warning types. An example of this customization: [TestingAndDebugging::ProhibitNoWarnings] allow = uninitialized once If a true value is specified for the "allow_with_category_restriction" option, then any "no warnings" that restricts the set of warnings that are turned off will pass. [TestingAndDebugging::ProhibitNoWarnings] allow_with_category_restriction = 1 SEE ALSO
Perl::Critic::Policy::TestingAndDebugging::RequireUseWarnings 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::TestingAndDebugging::ProhibitNoWarnings(3)
Man Page