perl::critic::policy::subroutines::protectprivatesubs(3) [centos man page]
Perl::Critic::Policy::Subroutines::ProtectPrivateSubs(3)User Contributed Perl DocumentatioPerl::Critic::Policy::Subroutines::ProtectPrivateSubs(3)NAME
Perl::Critic::Policy::Subroutines::ProtectPrivateSubs - Prevent access to private subs in other packages.
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
By convention Perl authors (like authors in many other languages) indicate private methods and variables by inserting a leading underscore
before the identifier. This policy catches attempts to access private variables from outside the package itself.
The subroutines in the POSIX package which begin with an underscore (e.g. "POSIX::_POSIX_ARG_MAX") are not flagged as errors by this
policy.
CONFIGURATION
You can define what a private subroutine name looks like by specifying a regular expression for the "private_name_regex" option in your
.perlcriticrc:
[Subroutines::ProtectPrivateSubs]
private_name_regex = _(?!_)w+
The above example is a way of saying that subroutines that start with a double underscore are not considered to be private. (Perl::Critic,
in its implementation, uses leading double underscores to indicate a distribution-private subroutine-- one that is allowed to be invoked by
other Perl::Critic modules, but not by anything outside of Perl::Critic.)
You can configure additional subroutines to accept by specifying them in a space-delimited list to the "allow" option:
[Subroutines::ProtectPrivateSubs]
allow = FOO::_bar FOO::_baz
These are added to the default list of exemptions from this policy. Allowing a subroutine also allows the corresponding method call. So
"FOO::_bar" in the above example allows both "FOO::_bar()" and "FOO->_bar()".
HISTORY
This policy is inspired by a similar test in B::Lint.
BUGS
Doesn't forbid "$pkg->_foo()" because it can't tell the difference between that and "$self->_foo()".
SEE ALSO
Perl::Critic::Policy::Variables::ProtectPrivateVars
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. 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::Subroutines::ProtectPrivateSubs(3)
Check Out this Related Man Page
Perl::Critic::Policy::RegularExpressions::RequireBracesFUserlContributed PerPerl::Critic::Policy::RegularExpressions::RequireBracesForMultiline(3)NAME
Perl::Critic::Policy::RegularExpressions::RequireBracesForMultiline - Use "{" and "}" to delimit multi-line regexps.
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
Long regular expressions are hard to read. A good practice is to use the "x" modifier and break the regex into multiple lines with
comments explaining the parts. But, with the usual "//" delimiters, the beginning and end can be hard to match, especially in a "s///"
regexp. Instead, try using "{}" characters to delimit your expressions.
Compare these:
s/
<a s+ href="([^"]+)">
(.*?)
</a>
/link=$1, text=$2/xms;
vs.
s{
<a s+ href="([^"]+)">
(.*?)
</a>
}
{link=$1, text=$2}xms;
Is that an improvement? Marginally, but yes. The curly braces lead the eye better.
CONFIGURATION
There is one option for this policy, "allow_all_brackets". If this is true, then, in addition to allowing "{}", the other matched pairs of
"()", "[]", and "<>" are allowed.
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.16.32014-06-Perl::Critic::Policy::RegularExpressions::RequireBracesForMultiline(3)