All in all, I wonder if there is ever a situation where the ST makes sense?

Over plain sort, sure. Over GRT? Not so much.

ST can return objects, whereas GRT returns strings unless an external array is used.

ST can produce simpler and more readable code than GRT in some circumstances.

However, ST isn't as fast as GRT. 

# ST
my @fhs =
   map $_->[0],
   sort { $a->[1] <=> $b->[1] }
   map [ $_, fileno($_) ],
   get_fhs();

[download]
# GRT
my @fhs = get_fhs();
@fhs =
   map $fhs[ unpack('x4 N', $_) ]
   sort
   map pack('NN', fileno($fhs[$_]), $_),
   0..$#fhs;

[download]
# GRT
my @fhs = get_fhs();
@fhs = @fhs[
   map unpack('x4 N', $_),
   sort
   map pack('NN', fileno($fhs[$_]), $_),
   0..$#fhs
];

[download]

In reply to Re^3: Array Sort by ikegami
in thread Array Sort by gopalr

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.