IMO, the only thing wrong with the regexp approach used in some responses was forgetting to include the optional \.*\d* in the number being read in for sorting (I also made some style and performance adjustments to the sort algorithm, i.e. the use of a subroutine and an orcish manoeuvre) 
perl -w -MData::Dumper -e '
@old = ( "10.5 AA", "9 AC", "2 BB");
%orcish = ();
@new = sort {($orcish{$b} ||= ForceFloat($b)) <=> ($orcish{$a} ||= For
+ceFloat($a))} @old; 
print Dumper \@new;
sub ForceFloat{
    return $_[0] =~ /(\d+\.*\d*)/ ? $1 : 0.0;
}'

[download]

-M

Free your mind

In reply to Re: Numeric Sort for Stringified Value (How to Avoid Warning) by Moron
in thread Numeric Sort for Stringified Value (How to Avoid Warning) by neversaint

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.