bradcathey,
Your getinfo example doesn't reflect what expensive operations you are trying to avoid nor have you indicated what level of visibility (scope) you need. To summarize the examples provided so far:
- Memoization: The sub is only invoked once per unique set of arguments while subsequent invocations hit cache
- Raise Scope: The return values are elevated in scope so that they can be seen by all subs in the package. This can be simplified by storing in a hash
- Convert Return Values To Hash: This is the solution from fglock that you appear to like. This only simplifies the retrieval process, you are still building the hash with whatever expensive operations you have each time it is called
- Hashref, Singleton, Object: These are all variations on item 2. Depending on implementation you can defer expensive operation until requested
Without knowing more information, I would make a few assumptions and not have a getinfo() sub at all.
#package declaration if applicable
my %info = (
name => expensive_op1(),
address => expensive_op2(),
);
# later on in the code
sub routine_A {
print $info{name};
}
-
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.
|
