There seems to be very little on the function "our" in manuals and tutorials.
This observation is correct, and that's because there are few if any projects that are not improved by a global s/our/my/.
Of course that will break your existing system of letting everybody share the same global variable. This is generally considered a good thing.
In the file where you declare and populate my %prod, follow it up with an offer to share:
sub get_prod_ref {
return \%prod;
}
and now let client files say
use My::Configuration;
my $prod_ref = My::Configuration::get_prod_ref();
# or if you prefer
my %prod = %{ My::Configuration::get_prod_ref() };
-
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.
|