You understand sort well, so there's not much efficiency to be gained, I think.
However, I would have used some complex data structure for readability. This also removes the need for temporary variables. (but adds an array)
my @data =
sort {
$a->[7] cmp $b->[7] ||
$b->[6] <=> $a->[6] || # '' == 0
$a->[0] <=> $b->[0] ||
$a->[1] <=> $b->[1] ||
$a->[2] <=> $b->[2] ||
$a->[4] cmp $b->[4] ||
$a->[3] cmp $b->[3]
} map {
[ /^(\d+)(\D+)(\d+)(\D*)R(\d+)(B?)(\d*)\.(\w+)$/ ]
} <DATA>;
print "$_->[0]$_->[1]$_->[2]$_->[3]R$_->[4]$_->[5]$_->[6].$_->[7]\n" f
+or @data;
I've made some mistake in there, but I leave it up to you to find and fix it. For some reason, my version puts 113B28R2.ras two places too high (top==0) in the array.
I think my version is more readable, and threrefore more reliable and maintainable (if the bug is fixed, that is ;))
2;0 juerd@ouranos:~$ perl -e'undef christmas'
Segmentation fault
2;139 juerd@ouranos:~$
-
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.
|