If you'll forgive some general remarks only tangentially related to your question -- to add to what tye said, they say that premature optimization is the root of all evil. I think it's generally better to write a program in the way that most clearly and naturally expresses what you want it to do, that's most maintainable and so on; optimize only when it's necessary and worthwhile, and then profile to see where the hotspots are and focus on those, not on what looks most ripe for optimization. And always: measure, measure, measure.
Disclaimer: I'm not a programmer or in fact any kind of IT pro, I just occasionally use Perl because it helps me solve problems.
-
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.
|
