So is it more efficent (correct?) to store output in a scalar and then "print" it when your done generating output or to make several prints.

Do the simplest thing that works. Then, if there proves to be a performance problem, profile (measure) before deciding what to do. Optimizing before you have data is almost always a waste of time. And once you have the data, you'll often find that the issue is algorithmic.

I often gather up strings into a scalar for later printing, and though I've often daydreamed up super-efficient way of doing this, the applications always either seem to be fast enough, or the performance issues are solved by doing a more effective query against the database.

In reply to Re: Optimizing Output by dws
in thread Optimizing Output by Dogma

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.