"premature optimization is the root of all evil"
The key is premature optimization. You can easily spend lots of time and money optimizing code that has no bearing whatsoever on the actual performance of your program! For example, i/o might take 2 minutes, and sorting the data takes 1 millisecond. Who cares if a different sorting algorithm will cut the sort time in half - optimize the i/o and forget about the sort. Profile your program, then optimize the bottlenecks.

That being said, pointless optimization of a problem to see who comes up with the fastest algorithm, that sounds like fun and a great way to learn a little more about the language!

In reply to Re: Golfing and Sprinting by bmann
in thread Golfing and Sprinting by kvale

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.