The result is that just by using one module you can pull in half of the code base.

So, is that a problem? Or asked differently, what kind of problem are you actually trying to solve?

Does your application use too much memory? or is the startup time too large?

If you don't have a problem, don't worry. Remember Donald Knuth's wisdom: "premature optimization is the root of all evil".

The reason that this "don't use stuff that you don't need the namespace of" thing sounds weird to me is that I don't think it works. In your example above, $order comes somewhere. Wherever it comes from, that module actually loaded the module Order - probably at compile time, and unconditionally. So it gets compile once anyway - and if you use use it multiple times from different places, it's still only compiled once.


In reply to Re: general rule for using use by moritz
in thread general rule for using use by perl5ever

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.