Well, I felt it vitally important to see exactly how much of an improvement this really is so I benchmarked it: 

Benchmark: running tilly_l, tilly_s, tye_l, tye_s, each for at least 3
+ CPU seconds...
Out of memory!

[download]
Oops. Um, let me try that again: 
Benchmark: running tilly_l, tilly_s, tye_l, tye_s, each for at least 3
+ CPU seconds...
   tilly_l:  5.14 CPU @  0.39/s (n=2)
            (warning: too few iterations for a reliable count)
   tilly_s:  3.25 CPU @ 18.44/s (n=60)
     tye_l:  3.16 CPU @ 443.43/s (n=1403)
     tye_s:  3.25 CPU @ 1691.22/s (n=5488)

[download]
Ah, yes, an admirable improvement. But my code still looks nicer, which was the point.

So I win this round... ; )

        - tye (but my friends call me "Tye")

In reply to (tye)Re3: sum of counts by tye
in thread sum of counts by tye

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.