Albeit the Schwarzian transform is a clever solution, user-programmers can suffer from the rule that ready-made solutions are apt to break at the slightest deviation from the requirement they originally met. I am not saying this is a particularly flagrant case, but as a rule, instead of hacking away at a not-quite-fitting algorithm, it might be an idea to try to construct the solution more directly from the actual requirement, e.g.:
my %count; my @ulist = sort { ($count{ $b } ||= TabCount( $b ) ) <=> ($count{ $a } ||= TabCount( $a ) ) } values %unk; sub TabCount { $_ = shift; s/\s+$//; my @split = split /\t/; return $#split; }

-M

Free your mind


In reply to Re: Bogus variable to avoid 'split' warning by Moron
in thread Bogus variable to avoid 'split' warning by throop

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.