Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

Why don't you store the values individually as keys, and format them directly when printing?

I think of a structure ordered by "logical size" of each value:

Year -> Month -> Day -> Hour -> Minute -> Second
%Date_Time = ( Year => { Month => { Day => { Hour => { Minute => { Second => 1, }, }, }, }, }, ); for my $year ( sort keys %Date_Time ) { for my $month ( sort keys %{ $Date_Time{$year} } ) { for my $day ( sort keys %{ $Date_Time{$year}->{$month} } ) { my $time_r = $Date_Time{$year}->{$month}->{$day}; for my $hour ( sort keys %$time_r ) { for my $minute ( sort keys %{ $time_r->{$hour} } ) { for my $second ( sort keys %{ $time_r->{$hour}->{$minute} } +) { printf "Date: %d-%d-%d %02d:%02d:%02d\n", $day, $month, $year, $hour, $minute, $second; } } } } }

In reply to Re: Sort Hash array using date by linuxer
in thread Sort Hash array using date by madtoperl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.