Perl::Critic::Policy::Subroutines::ProhibitReturnSort - Behavior of C is not defined if called in scalar context.


Perl-Critic documentation  | view source Contained in the Perl-Critic distribution.

Index


NAME

Top

Perl::Critic::Policy::Subroutines::ProhibitReturnSort - Behavior of sort is not defined if called in scalar context.

AFFILIATION

Top

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

DESCRIPTION

Top

The behavior of the builtin sort function is not defined if called in scalar context. So if you write a subroutine that directly returns the result of a sort operation, then you code will behave unpredictably if someone calls your subroutine in a scalar context. This Policy emits a violation if the return keyword is directly followed by the sort function. To safely return a sorted list of values from a subroutine, you should assign the sorted values to a temporary variable first. For example:

   sub frobulate {

       return sort @list;  # not ok!

       @sorted_list = sort @list;
       return @sort        # ok
   }

KNOWN BUGS

Top

This Policy is not sensitive to the wantarray function. So the following code would generate a false violation:

   sub frobulate {

       if (wantarray) {
           return sort @list;
       }
       else{
           return join @list;
       }
   }

CONFIGURATION

Top

This Policy is not configurable except for the standard options.

CREDITS

Top

This Policy was suggested by Ulrich Wisser and the http://iis.se team.

AUTHOR

Top

Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>

COPYRIGHT

Top


Perl-Critic documentation  | view source Contained in the Perl-Critic distribution.