The best way to find out is to profile the code to see which satisfy your optimality criteria. Which you haven't specified BTW. The first may be slightly slower but may also use less memory. What are you trying to optimize?

However, the first question that comes to my mind is "Why do you care?" Premature optimization is the root of all evil. The best thing to do is separate your program logic from your presentation logic, so you should really be using some sort of templating system. Most templating systems take care of handling the output for you so you don't have to worry about doing it piecemeal. :-)

duff

In reply to Re: Many prints of small string or one print of huge string? by duff
in thread Many prints of small string or one print of huge string? by dmitryrusak

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.