It looks like you're looking for inheritance. In My::Module do: 
our @ISA = qw(My::Module::This My::Module::That);

[download]
Without knowing the details of what you're doing, I strongly recommend that you learn about the benefits of modularity. Which does not mean labeling chunks of stuff "modules". But instead means dividing your program into pieces that do different things, then making the interfaces between those pieces be small and clear. Which means that you're then able to make large changes to individual pieces.

I say this because writing down all of the functions that do one thing in one place, then freely using them everywhere else exports a large interface. This is bad for modularity, and is why Exporter advises you not to do that. To see just one of the practical problems that result, pity the poor maintenance programmer who wants to see how a commonly used function is implemented. The programmer knows that that function can be called in a particular package, but if that package has tons of imported functions from elsewhere, then tracking down the original function can be a real PITA.

This same issue is why many good programmers think that inheritance is overused and it is better to use other techniques, like composition, instead.

In reply to Re: How do I organize a large module? by tilly
in thread How do I organize a large module? by hesco

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.