Just so you know,
require() doesn't happen until run-time, so I don't see the need for the
BEGIN block. Anyway, here's how I would construct a sort function... maybe I love regexes too much?
# assume my(%field) exists, holding name->index pairs
# assume my(@records) exists, holding your recods
my $data = "lnum-a,source-a,hits-d,sip-d,time-a";
my %is_string = ( source => 1 ); # sort with cmp
my $sorter = make_field_sort($data, \%field, \%is_string);
for (sort $sorter @records) { ... }
sub make_field_sort {
my ($data, $FIELD, $STRING) = @_;
my @cmp;
for (split /,/, $data) {
my ($f, $o) = split /-/;
push @cmp, ('b <=> a', 'a <=> b')[$o eq 'a'];
$cmp[-1] =~ s/<=>/cmp/ if $STRING->{$f};
$cmp[-1] =~ s/([ab])/\$${1}->[$FIELD->{$f}]/g;
}
local $" = " or ";
eval "sub { @cmp }";
}
_____________________________________________________
Jeff[japhy]Pinyan:
Perl,
regex,
and perl
hacker.
s++=END;++y(;-P)}y js++=;shajsj<++y(p-q)}?print:??;
-
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.