If you Export the variables, then you don't need to declare them at all in your script. :-)

Exactly ;-)

I grant that it is fairly rare that you need to have 2 different files with code in the same package. But it does happen from time to time. For example you might encounter that at a first pass in refactoring some spaghetti. For another example some modules may need to autogenerate code in another package's namespace. In those situations it is better to use vars than to declare with our.

Fair enough. You may have even convinced me to use vars a bit more than I do now; I'll keep it in mind the next time these kinds of scenarios come along.

For my part, though, I would suggest that using our keeps down code smell (like spreading packages over multiple files). The fact that it makes those kinds of constructs harder is IMHO a feature. YMMV depending on context, of course :-)

---

---

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.