[gitmo/Perl-Critic-Dynamic-Moose.git] / lib / Perl / Critic / Dynamic / Moose.pod

=pod

=head1 NAME

Perl::Critic::Dynamic::Moose

=head1 DESCRIPTION

=head1 WARNING

B<VERY IMPORTANT:> Most L<Perl::Critic> Policies (including all the ones that
ship with Perl::Critic> use pure static analysis -- they never compile nor
execute any of the code that they analyze.  However, this policy is very
different.  It actually attempts to compile your code and then compares the
subroutines mentioned in your code to those found in the symbol table.
Therefore you should B<not> use this Policy on any code that you do not trust,
or may have undesirable side-effects at compile-time (such as connecting to the
network or mutating files).

For this Policy to work, all the modules included in your code must be
installed locally, and must compile without error.
=head1 AUTHOR

Shawn M Moore, C<sartak@bestpractical.com>

=cut
Commit	Line	Data
d7b8852e	1	=pod
	2
	3	=head1 NAME
	4
	5	Perl::Critic::Dynamic::Moose
	6
ea5503e8	7	=head1 DESCRIPTION
	8
	9	=head1 WARNING
	10
	11	B<VERY IMPORTANT:> Most L<Perl::Critic> Policies (including all the ones that
	12	ship with Perl::Critic> use pure static analysis -- they never compile nor
	13	execute any of the code that they analyze. However, this policy is very
	14	different. It actually attempts to compile your code and then compares the
	15	subroutines mentioned in your code to those found in the symbol table.
	16	Therefore you should B<not> use this Policy on any code that you do not trust,
	17	or may have undesirable side-effects at compile-time (such as connecting to the
	18	network or mutating files).
	19
	20	For this Policy to work, all the modules included in your code must be
	21	installed locally, and must compile without error.
e556eafb	22	=head1 AUTHOR
	23
	24	Shawn M Moore, C<sartak@bestpractical.com>
	25
d7b8852e	26	=cut
d7b8852e	27