Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

perl::critic::policy::variables::prohibitpunctuationvars(3pm) [debian man page]

Perl::Critic::Policy::Variables::ProhibitPunctuationVarsUser)Contributed Perl DocumenPerl::Critic::Policy::Variables::ProhibitPunctuationVars(3pm)

NAME
Perl::Critic::Policy::Variables::ProhibitPunctuationVars - Write "$EVAL_ERROR" instead of "$@". AFFILIATION
This Policy is part of the core Perl::Critic distribution. DESCRIPTION
Perl's vocabulary of punctuation variables such as $!, $., and $^ are perhaps the leading cause of its reputation as inscrutable line noise. The simple alternative is to use the English module to give them clear names. $| = undef; #not ok use English qw(-no_match_vars); local $OUTPUT_AUTOFLUSH = undef; #ok CONFIGURATION
The scratch variables $_ and @_ are very common and are pretty well understood, so they are exempt from this policy. The same goes for the less-frequently-used default filehandle "_" used by stat(). All the regexp capture variables ($1, $2, ...) are exempt too. $] is exempt because there is no English equivalent and Module::CoreList is based upon it. You can add more exceptions to your configuration. In your perlcriticrc file, add a block like this: [Variables::ProhibitPunctuationVars] allow = $@ $! The "allow" property should be a whitespace-delimited list of punctuation variables. Other configuration options control the parsing of interpolated strings in the search for forbidden variables. They have no effect on detecting punctuation variables outside of interpolated strings. [Variables::ProhibitPunctuationVars] string_mode = thorough The option "string_mode" controls whether and how interpolated strings are searched for punctuation variables. Setting "string_mode = thorough", the default, checks for special cases that may look like punctuation variables but aren't, for example $#foo, an array index count; $$bar, a scalar dereference; or $::baz, a global symbol. Setting "string_mode = disable" causes all interpolated strings to be ignored entirely. Setting "string_mode = simple" uses a simple regular expression to find matches. In this mode, the magic variables $$, "$'", $# and $: are ignored within interpolated strings due to the high risk of false positives. Simple mode is retained from an earlier draft of the interpolated- strings code. Its use is only recommended as a workaround if bugs appear in thorough mode. The "string_mode" option will go away when the parsing of interpolated strings is implemented in PPI. See "CAVEATS" below. BUGS
Punctuation variables that confuse PPI's document parsing may not be detected correctly or at all, and may prevent detection of subsequent ones. In particular, $" is known to cause difficulties in interpolated strings. CAVEATS
ProhibitPunctuationVars relies exclusively on PPI to find punctuation variables in code, but does all the parsing itself for interpolated strings. When, at some point, this functionality is transferred to PPI, ProhibitPunctuationVars will cease doing the interpolating and the "string_mode" option will go away. 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.14.2 2012-06-07 Perl::Critic::Policy::Variables::ProhibitPunctuationVars(3pm)

Check Out this Related Man Page

Perl::Critic::Policy::Variables::ProhibitPackageVars(3) User Contributed Perl DocumentationPerl::Critic::Policy::Variables::ProhibitPackageVars(3)

NAME
Perl::Critic::Policy::Variables::ProhibitPackageVars - Eliminate globals declared with "our" or "use vars". AFFILIATION
This Policy is part of the core Perl::Critic distribution. DESCRIPTION
Conway suggests avoiding package variables completely, because they expose your internals to other packages. Never use a package variable when a lexical variable will suffice. If your package needs to keep some dynamic state, consider using an object or closures to keep the state private. This policy assumes that you're using "strict vars" so that naked variable declarations are not package variables by default. Thus, it complains you declare a variable with "our" or "use vars", or if you make reference to variable with a fully-qualified package name. $Some::Package::foo = 1; # not ok our $foo = 1; # not ok use vars '$foo'; # not ok $foo = 1; # not allowed by 'strict' local $foo = 1; # bad taste, but technically ok. use vars '$FOO'; # ok, because it's ALL CAPS my $foo = 1; # ok In practice though, its not really practical to prohibit all package variables. Common variables like $VERSION and @EXPORT need to be global, as do any variables that you want to Export. To work around this, the Policy overlooks any variables that are in ALL_CAPS. This forces you to put all your exported variables in ALL_CAPS too, which seems to be the usual practice anyway. CONFIGURATION
There is room for exceptions. Some modules, like the core File::Find module, use package variables as their only interface, and others like Data::Dumper use package variables as their most common interface. These module can be specified from your .perlcriticrc file, and the policy will ignore them. [Variables::ProhibitPackageVars] packages = Data::Dumper File::Find FindBin Log::Log4perl This is the default setting. Using "packages =" will override these defaults. You can also add packages to the defaults like so: [Variables::ProhibitPackageVars] add_packages = My::Package You can add package "main" to the list of packages, but that will only OK variables explicitly in the "main" package. SEE ALSO
Perl::Critic::Policy::Variables::ProhibitPunctuationVars Perl::Critic::Policy::Variables::ProhibitLocalVars 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::ProhibitPackageVars(3)
Man Page