perl::critic::more(3) [centos man page]

Perl::Critic::More(3)					User Contributed Perl Documentation				     Perl::Critic::More(3)

NAME

       Perl::Critic::More - Supplemental policies for Perl::Critic

SYNOPSIS

	 perl -MCPAN -e'install Perl::Critic::More'
	 perlcritic -theme more lib/Foo.pm

AFFILIATION

       This file has no functionality, but instead is a placeholder for a loose collection of Perl::Critic policies.  All of those policies will
       have an "Affiliation" section announcing their participation in this grouping.

DESCRIPTION

       This is a collection of Perl::Critic policies that are not included in the Perl::Critic core for a variety of reasons:

       o   Experimental

	   Some policies need some time to work out their kinks, test usability, or gauge community interest.  A subset of these will end up in
	   the core Perl::Critic someday.

       o   Requires special dependencies

	   For example, some policies require development versions of PPI (or some other CPAN module).	These will likely end up in the
	   Perl::Critic core when their dependencies are fulfilled.

       o   Peripheral to Perl

	   For example, the "Editor::RequireEmacsFileVariables" policy is metacode.  These are not part of Perl::Critic's mission.

       o   Special purpose

	   For example, policies like "CodeLayout::RequireASCII" designed to scratch itches not felt by most of the community.	These will always
	   remain in a Perl::Critic supplement instead of in the core.

       All of these policies have the theme "more" so they can be turned off as a group via .perlcriticrc by adding this line:

	 theme = not more

       The special purpose ones may be part of the "notrecommended" theme.  Avoid these via:

	 theme = not notrecommended

       Sorry about the double-negative...  See "CONFIGURATION" in Perl::Critic for details on how to interact with themes.

SEE ALSO

       Perl::Critic

       Perl::Critic::Bangs - Andy Lester's fantastic list of code pet peeves

       Perl::Critic::Lax - RJBS' more-lenient versions of some core Perl::Critic policies

       parrot - the parrot team has developed a few specialized Perl::Critic policies of their own

AUTHOR

       Chris Dolan <cdolan@cpan.org>

       The included policies may have other authors -- please see them individually.

       This distribution is controlled by the Perl::Critic team.  If you want to add a policy to this collection, check out our Subversion
       repository and mailing lists at <http://perlcritic.tigris.org>.

COPYRIGHT

       Copyright (c) 2006-2008 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-10						     Perl::Critic::More(3)

Check Out this Related Man Page

Perl::Critic::Policy::Subroutines::ProtectPrivateSubs(3pUser Contributed Perl DocumentatPerl::Critic::Policy::Subroutines::ProtectPrivateSubs(3pm)

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.14.2							    2012-06-07		Perl::Critic::Policy::Subroutines::ProtectPrivateSubs(3pm)

Linux and UNIX Man Pages

perl::critic::more(3) [centos man page]

Check Out this Related Man Page