Browse files

headerdep: perlcritic warning

Minor perlcritic warning: "return" statement with explicit "undef" at line 84, column 2.  See page 199 of PBP.  (Severity: 5)

The rationale according to PBP is that an explicit return of undef
(contrary to most people's expectations) doesn't
always evaluate as false. It has to with the fact that perl return value
depends on context the function is called. If function is used in
list context, the appropriate return value for false is an empty list;
whereas in scalar context the return value for false is undefined.
By just using a "return" both cases are handled.

In the context of a trivial script this doesn't matter. But one script
may be cut-paste into later code (most people like me only know 50%
of perl), that is why perlcritic always complains

Signed-off-by: Stephen Hemminger <>
Signed-off-by: Michal Marek <>
  • Loading branch information...
1 parent 2d74b2c commit 1dcd81002453f9f22c6c4fd6c3c7d8f1c7c891fa Stephen Hemminger committed with michal42 Mar 8, 2010
Showing with 1 addition and 2 deletions.
  1. +1 −2 scripts/
@@ -80,8 +80,7 @@ sub search {
my $path = "$i/$filename";
return $path if -f $path;
- return undef;
+ return;
sub parse_all {

0 comments on commit 1dcd810

Please sign in to comment.