Perhaps version. Also see the -k and other sorting options in the unix sort options.

If neither of those solve your issue, then perhaps this sort routine:

# Assume: version strings have same numbers of parts.  Adjust if not.
# Note: This is not efficient, but may help explain what needs to happ
+en.
sort {
    my @a_fn_parts  = split( qr([_]), $a );
    my @a_ver_parts = split( qr([.]), @a_fn_parts[1] );

    my @b_fn_parts  = split( qr([_]), $b );
    my @b_ver_parts = split( qr([.]), @b_fn_parts[1] );

    my $i = 0;
    while ( $i < @a_ver_parts ) {
        return $a_ver_parts[ $i ] <=> $b_ver_parts[ $i ]
            if ( $a_ver_parts[ $i ] != $b_ver_parts[ $i ] );
        $i++;
    }
    return 0;
}

[download]

--MidLifeXis

In reply to Re: File Parsing by MidLifeXis
in thread File Parsing by kel

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


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.