Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

perl::critic::policy::builtinfunctions::prohibitstringyeval(3pm) [debian man page]

Perl::Critic::Policy::BuiltinFunctions::ProhibitStringyEUser3Contributed Perl DocuPerl::Critic::Policy::BuiltinFunctions::ProhibitStringyEval(3pm)

NAME

       Perl::Critic::Policy::BuiltinFunctions::ProhibitStringyEval - Write "eval { my $foo; bar($foo) }" instead of "eval "my $foo; bar($foo);"".

AFFILIATION

       This Policy is part of the core Perl::Critic distribution.

DESCRIPTION

       The string form of "eval" is recompiled every time it is executed, whereas the block form is only compiled once.  Also, the string form
       doesn't give compile-time warnings.

	   eval "print $foo";	     # not ok
	   eval {print $foo};	     # ok

CONFIGURATION

       There is an "allow_includes" boolean option for this Policy.  If set, then strings that look like they only include a single "use" or
       "require" statement (with the possible following statement that consists of a single number) are allowed.  With this option set, the
       following are flagged as indicated:

	   eval 'use Foo';	       # ok
	   eval 'require Foo';	       # ok
	   eval "use $thingy;";        # ok
	   eval "require $thingy;";    # ok
	   eval "use $thingy; 1;";     # ok
	   eval "require $thingy; 1;"; # ok

	   eval 'use Foo; blah;';      # still not ok
	   eval 'require Foo; 2; 1;';  # still not ok
	   eval 'use $thingy;';        # still not ok
	   eval 'no Foo';	       # still not ok

       If you don't understand why the number is allowed, see Perl::Critic::Policy::ErrorHandling::RequireCheckingReturnValueOfEval.

       This option inspired by Ricardo SIGNES' Perl::Critic::Policy::Lax::ProhibitStringyEval::ExceptForRequire.

SEE ALSO

       Perl::Critic::Policy::ControlStrucutres::RequireBlockGrep

       Perl::Critic::Policy::ControlStrucutres::RequireBlockMap

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::BuiltinFunctions::ProhibitStringyEval(3pm)

Check Out this Related Man Page

Perl::Critic::Policy::Variables::ProhibitLocalVars(3pm) User Contributed Perl DocumentationPerl::Critic::Policy::Variables::ProhibitLocalVars(3pm)

NAME

       Perl::Critic::Policy::Variables::ProhibitLocalVars - Use "my" instead of "local", except when you have to.

AFFILIATION

       This Policy is part of the core Perl::Critic distribution.

DESCRIPTION

       Since Perl 5, there are very few reasons to declare "local" variables.  The most common exceptions are Perl's magical global variables.	If
       you do need to modify one of those global variables, you should localize it first.  You should also use the English module to give those
       variables more meaningful names.

	   local $foo;	 #not ok
	   my $foo;	 #ok

	   use English qw(-no_match_vars);
	   local $INPUT_RECORD_SEPARATOR    #ok
	   local $RS			    #ok
	   local $/;			    #not ok

CONFIGURATION

       This Policy is not configurable except for the standard options.

NOTES

       If an external module uses package variables as its interface, then using "local" is actually a pretty sensible thing to do.  So
       Perl::Critic will not complain if you "local"-ize variables with a fully qualified name such as $Some::Package::foo.  However, if you're in
       a position to dictate the module's interface, I strongly suggest using accessor methods instead.

SEE ALSO

       Perl::Critic::Policy::Variables::ProhibitPunctuationVars

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::ProhibitLocalVars(3pm)
Man Page