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;
}

[download]

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() };

[download]

In reply to Abandon "our" declarations (was: Re: our scope and packages) by Narveson
in thread our scope and packages by jfrm

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.