thinker's solution is perfectly valid. However it's probably not the most efficient way to do it. This may be a concern if you have a lot of data.
So, I'll suggest using a Schwartzian Transform (an algorithm created by our very own merlyn).
untested code:
#!/usr/bin/perl -w
use strict;
open (DATA, "./data.txt") or die $!; # for example
my @sorted = map { $_->[1] }
sort { $a->[0] cmp $b->[0] }
map { [ &fix_date($_), $_ ] } <DATA>;
for (@sorted) { print $_ };
sub fix_date {
my ($d,$m,$y) = ( shift =~ m|(\d\d)/(\d\d)/(\d{4})| );
return "$y-$m-$d";
}
The basic speed eater for
thinker's way is that you have
to munge the date to sort it a great number of times.
The first (lower) map does the time expensive data munging, into a form that's easy for sort to deal with, and the last (top) map puts the data back into the original form
HTH
/\/\averick
perl -l -e "eval pack('h*','072796e6470272f2c5f2c5166756279636b672');"
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.