What tobyink said. An example where I always choose require and put it in subs/methods is the admin functions in webapps. Most of an application’s users can’t even see the admin code so there is no point in taking the hit on all requests. Plus you can be less worried about bringing in many/heavy/slow modules–
use AllUserStuff;
sub admin_stuff {
require HugeExpensiveCodeRarelyEverCalled;
require ManyMoreOtheSame;
...
}
Just make sure to write good tests around it so you don’t get the run time surprises you mentioned.
-
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.
|
