I don't know which will be faster, I very strongly suspect that there will be no difference at all between them. As previously mentioned, though, the only way to tell for sure would be to use the Benchmark module.

With your second example, though, once you close the FILE filehandle, you will also have a closed STDOUT - which means that you will no longer see anything printed to STDOUT.

You can get around this with the "local" operator, though. Something like this:-

print "Hello World!\n"; { open (FILE, ">bob.txt"); local *STDOUT = *FILE; print "this is text\n"; close FILE; print "You will never see this\n"; } print "You will see this though\n";

In reply to Re: Speed comparison between printing to STDOUT and printing to a filehandle by dtr
in thread Speed comparison between printing to STDOUT and printing to a filehandle by sberthold

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.