First, I would generally avoid using a module-global array. This is because there are plenty of functions which modify the array and thus if you suddenly end up with paths missing you have to figure out what shifted or popped your array. That could be a lot of fun, not....

So while it is true you can declare the array with "our" scope and access it with a fully qualified scope, this strikes me as fairly brittle because such access is read-write.

For this reason I would certainly recommend declaring the array with a "my" scope and having a function that returns a copy of the array. Something like:

my @paths;
sub get_paths {
    init_paths unless @paths;
    return @paths;
}
sub init_paths {
    ... # logic to initialize your path list
}
[download]

Note this passes the array back by values and thus effectively gives other modules read-only access to it.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.