Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

perl::prereqscanner::scanner::perl5(3pm) [debian man page]

Perl::PrereqScanner::Scanner::Perl5(3pm)		User Contributed Perl Documentation		  Perl::PrereqScanner::Scanner::Perl5(3pm)

NAME
Perl::PrereqScanner::Scanner::Perl5 - scan for core Perl 5 language indicators of required modules VERSION
version 1.012 DESCRIPTION
This scanner will look for the following indicators: o plain lines beginning with "use" or "require" in your perl modules and scripts, including minimum perl version o regular inheritance declared with the "base" and "parent" pragmata Since Perl does not allow you to supply a version requirement with a "require" statement, the scanner will check the statement after the "require Module" to see if it is "Module->VERSION( minimum_version );". In order to provide a minimum version, that method call must meet the following requirements: o it must be the very next statement after "require Module". Nothing can separate them but whitespace and comments (and one semicolon). o "Module" must be a bareword, and match the "require" exactly. o "minimum_version" must be a literal number, v-string, or single-quoted string. Double quotes are not allowed. AUTHORS
o Jerome Quelin o Ricardo Signes <rjbs@cpan.org> COPYRIGHT AND LICENSE
This software is copyright (c) 2009 by Jerome Quelin. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.14.2 2012-06-27 Perl::PrereqScanner::Scanner::Perl5(3pm)

Check Out this Related Man Page

Perl::Critic::Policy::Modules::ProhibitConditionalUseStaUsernContributed Perl Perl::Critic::Policy::Modules::ProhibitConditionalUseStatements(3pm)

NAME
Perl::Critic::Policy::Modules::ProhibitConditionalUseStatements - Avoid putting conditional logic around compile-time includes. AFFILIATION
This Policy is part of the core Perl::Critic distribution. DESCRIPTION
Modules included via "use" are loaded at compile-time. Placing conditional logic around the "use" statement has no effect on whether the module will be loaded. Doing so can also serve to confuse the reader as to the author's original intent. If you need to conditionally load a module you should be using "require" instead. This policy will catch the following forms of conditional "use" statements: # if-elsif-else if ($a == 1) { use Module; } if ($a == 1) { } elsif ($a == 2) { use Module; } if ($a == 1) { } else { use Module; } # for/foreach for (1..$a) { use Module; } foreach (@a) { use Module; } # while while ($a == 1) { use Module; } # unless unless ($a == 1) { use Module; } # until until ($a == 1) { use Module; } # do-condition do { use Module; } if $a == 1; do { use Module; } while $a == 1; do { use Module; } unless $a == 1; do { use Module; } until $a == 1; # operator-do $a == 1 || do { use Module; }; $a == 1 && do { use Module; }; $a == 1 or do { use Module; }; $a == 1 and do { use Module; }; # non-string eval eval { use Module; }; Including a module via "use" in bare blocks, standalone do blocks, or string evals is allowed. # bare block { use Module; } # do do { use Module; } # string eval eval "use Module"; CONFIGURATION
This Policy is not configurable except for the standard options. AUTHOR
Peter Guzis <pguzis@cpan.org> COPYRIGHT
Copyright (c) 2010-2011 Peter Guzis. 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.14.2 2012-06-07Perl::Critic::Policy::Modules::ProhibitConditionalUseStatements(3pm)
Man Page

Featured Tech Videos