In your code you have to duplicate two copies of every message you print in your source; if you ever need to change the output you'd have to edit each copy of each pair of prints. It's left as an exercise to imagine the fun that commences when one or more inevitably gets out of sync and you have different results in different places for the "same" output. To say nothing of 7 months down the line when marketing wants the output also sent to a third and fourth place . . .

Using the subs (or the IO::Tee module or tee externally) you have to change just one string to affect the output to every destination.

--
We're looking for people in ATL

In reply to Re^4: Copy STDOUT and STDERR to logfile and also display to screen by Fletch
in thread Copy STDOUT and STDERR to logfile and also display to screen by boat73

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.