Perl 5 version 32.0 documentation

sort

NAME

sort - perl pragma to control sort() behaviour

SYNOPSIS

  1.     use sort 'stable';		# guarantee stability
  2.     use sort 'defaults';	# revert to default behavior
  3.     no  sort 'stable';		# stability not important
  5.     my $current;
  6.     BEGIN {
  7. 	$current = sort::current();	# identify prevailing pragmata
  8.     }

DESCRIPTION

With the sort pragma you can control the behaviour of the builtin sort() function.

A stable sort means that for records that compare equal, the original input ordering is preserved. Stability will matter only if elements that compare equal can be distinguished in some other way. That means that simple numerical and lexical sorts do not profit from stability, since equal elements are indistinguishable. However, with a comparison such as

  1.    { substr($a, 0, 3) cmp substr($b, 0, 3) }

stability might matter because elements that compare equal on the first 3 characters may be distinguished based on subsequent characters.

Whether sorting is stable by default is an accident of implementation that can change (and has changed) between Perl versions. If stability is important, be sure to say so with a

  1.   use sort 'stable';

The no sort pragma doesn't forbid what follows, it just leaves the choice open. Thus, after

  1.   no sort 'stable';

sorting may happen to be stable anyway.

CAVEATS

As of Perl 5.10, this pragma is lexically scoped and takes effect at compile time. In earlier versions its effect was global and took effect at run-time; the documentation suggested using eval() to change the behaviour:

  1.   { eval 'no sort "stable"';      # stability not wanted
  2.     print sort::current . "\n";
  3.     @a = sort @b;
  4.     eval 'use sort "defaults"';   # clean up, for others
  5.   }
  6.   { eval 'use sort qw(defaults stable)';     # force stability
  7.     print sort::current . "\n";
  8.     @c = sort @d;
  9.     eval 'use sort "defaults"';   # clean up, for others
  10.   }

Such code no longer has the desired effect, for two reasons. Firstly, the use of eval() means that the sorting algorithm is not changed until runtime, by which time it's too late to have any effect. Secondly, sort::current is also called at run-time, when in fact the compile-time value of sort::current is the one that matters.

So now this code would be written:

  1.   { no sort "stable";      # stability not wanted
  2.     my $current;
  3.     BEGIN { $current = sort::current; }
  4.     print "$current\n";
  5.     @a = sort @b;
  6.     # Pragmas go out of scope at the end of the block
  7.   }
  8.   { use sort qw(defaults stable);     # force stability
  9.     my $current;
  10.     BEGIN { $current = sort::current; }
  11.     print "$current\n";
  12.     @c = sort @d;
  13.   }