Hi Mano_Man
I assume it is mostly a design decision:
- do you need the info in $toPrint later?
- is it a benefit to use the say/print at only one place?
- do you want to give error-messages as soon as possible?
In my experience, the performance-differences are neglectable (but your use-case might be different).
However I have experienced an issue in the past with redirecting the output to a file, using the > in a windows batch file:
IIRC it didn't work when printing a text that was too long - it seemed that the data was sent out by print was much faster than the
writing to the file. Unfortunately, I can't find the old script where this happened... but it might a thing you want to check/consider.
HTH, Rata
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|