This might be a situation where study might be helpful. Here's section from the docs:
Takes extra time to study SCALAR ($_ if unspecified) in anticipation
+of doing many pattern matches on the string before it is next modifie
+d. This may or may not save time, depending on the nature and number
+of patterns you are searching on, and on the distribution of characte
+r frequencies in the string to be searched--you probably want to comp
+are run times with and without it to see which runs faster. Those loo
+ps that scan for many short constant strings (including the constant
+parts of more complex patterns) will benefit most.
-xdg
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
-
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.
|