Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

perl::critic::policy::subroutines::prohibitexplicitreturnundef(3) [centos man page]

Perl::Critic::Policy::Subroutines::ProhibitExplicitReturUsereContributed Perl DocPerl::Critic::Policy::Subroutines::ProhibitExplicitReturnUndef(3)

NAME
Perl::Critic::Policy::Subroutines::ProhibitExplicitReturnUndef - Return failure with bare "return" instead of "return undef". AFFILIATION
This Policy is part of the core Perl::Critic distribution. DESCRIPTION
Returning "undef" upon failure from a subroutine is pretty common. But if the subroutine is called in list context, an explicit "return undef;" statement will return a one-element list containing "(undef)". Now if that list is subsequently put in a boolean context to test for failure, then it evaluates to true. But you probably wanted it to be false. sub read_file { my $file = shift; -f $file || return undef; #file doesn't exist! #Continue reading file... } #and later... if ( my @data = read_file($filename) ){ # if $filename doesn't exist, # @data will be (undef), # but I'll still be in here! process(@data); } else{ # This is my error handling code. # I probably want to be in here # if $filname doesn't exist. die "$filename not found"; } The solution is to just use a bare "return" statement whenever you want to return failure. In list context, Perl will then give you an empty list (which is false), and "undef" in scalar context (which is also false). sub read_file { my $file = shift; -f $file || return; #DWIM! #Continue reading file... } CONFIGURATION
This Policy is not configurable except for the standard options. NOTES
You can fool this policy pretty easily by hiding "undef" in a boolean expression. But don't bother trying. In fact, using return values to indicate failure is pretty poor technique anyway. Consider using "die" or "croak" with "eval", or the Error module for a much more robust exception-handling model. Conway has a real nice discussion on error handling in chapter 13 of PBP. SEE ALSO
There's a discussion of the appropriateness of this policy at <http://perlmonks.org/index.pl?node_id=741847>. 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::Subroutines::ProhibitExplicitReturnUndef(3)

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