Concerning, "Your code has the worse of both." It has the advantage of being very easy though. Have you used a computer where putting 10,000*100 things in memory was a problem in the last 20 years?

The advantage of perl is the simple implementations you can achieve, not its speed. If speed was that much of a problem, why not use C or assembler?

Don't get me wrong, the incremental approach you show is superior. Definitely. But it's not as easy and easy was the point of my "worse" code.

Lastly, since you got me in an argumentative and defensive mood: if you want to outperform both perl and piddles, just let the database do the work — which is the point of last part of my post.

In short: jeese...

-Paul

In reply to Re^5: Correlation plots by jettero
in thread Correlation plots by Win

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.