It's mildly ugly, but in fact it's not really slow or all that fattening :)
The only problem with it is that you're going to be carrying the Sort key after you no longer need it.
ST to the rescue!
sub computeSortKey {
my $aref=shift;
my $sort;
my $M = 100;
for (@{$aref}) {
$sort += $M * $_;
$M = $M / 100;
}
return $sort;
}
#Schwartzian Transform
@Tree = map {$_->[0]}
sort {$a->[1] <=> $b->[1]}
map {[ $_, computeSortKey($_->{Path})]}
@Tree;
Note that I don't have perl on this PC, so I can't double check the code for syntax errors, but I think that'll work for you.
The advantages of doing it this way are that
1) it's a well known idiom, so a lot of perl programmers will grok right away what you're trying to do, and
2) you don't keep the sort key around after you no longer need it, so it keeps @Tree relatively clean.
--
Mike
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|