In many other places, speed may not be so much of an issue
Not only that, but what "speed" means can vary wildly. Performance is not a simple, single variable that can be tweaked at will. There are so many variables at play that any widely general rule is going to be wrong some time or another.
Take this specific thread as an example. This is a classic case of micro-optimization. Certainly, using constant may be way, way faster than using Readonly. But what if the majority of an application's time is spent on network IO? Does the time it takes to resolve a constant really matter? It takes careful consideration and testing in the proper context to know for sure.
To be clear, I'm not poo-pooing optimization by any means. I'm just trying to point out that it's important to optimize the right thing.
-
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.
|
