comment on

The biggest expense is going to be if you have a very large @INC that you're searching across. If files are located further down in @INC, such as if you're loading stuff you installed from CPAN, or if some of your @INC directories are on NFS mounts, those are going a much longer time to resolve than any import/export stuff you're dealing with.

As for import/export stuff, I have a policy in my CPAN modules to never import stuff into my namespace, preferring instead to do the following:

use Scalar::Util ();

if ( Scalar::Util::reftype( $thing ) eq 'HASH' ) {
    # Do stuff here
}
[download]

This has a couple benefits (other than performance, which I wasn't thinking of) to my thinking:

Almost everything of mine is OO. Perl's OO treats all subroutines in a given namespace as methods in that class. I want to keep my classes as clean as possible, particularly if I want to have an AUTOLOAD.
External subroutines are immediately labelled as to where they come from for future maintainers. While some people aren't as thrilled by this, I have been stymied by automatic exports and where they came from.

My criteria for good software:

Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re: Do multiple use statements across module dependency hierarchies require as little expense as multiple require statements? by dragonchild
in thread Do multiple use statements across module dependency hierarchies require as little expense as multiple require statements? by leocharre

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:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.