Yes, very helpful.
I was anticipating a sub generator of some sort, where the hash and comparison function are passed in, and a new anonymous sub is returned. This sub could then be used in the code block position of the sort command.
Perhaps something like this, which steals some ideas from Choroba's post, though I've not tried it:
sub make_sort_sub {
my $coderef = shift;
my $hashref = shift;
my $sort_sub = sub { something goes here }
return $sort_sub;
}
my %hash = ( a => 5, b => 4, c => 3 );
my $keys_by_value = make_sort_sub(
{ $hashref->{$a} <=> $hashref->{$b} },
\%hash);
my @keys_sorted_by_value = sort $keys_by_value %hash;
Then $keys_by_value can be reused elsewhere on the same hash. But can't be used on a different hash. :(
Hmmm, I'm thinking there's not a really elegant solution.
-QM
--
Quantum Mechanics: The dreams stuff is made of
-
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.
|