For managing them while developing them, do whatever's easiest for you. As a general rule, that's usually the way Perl likes to work.

For CPAN, well, perl will read '::' as a directory separator. So making them actual directories is good practice.

Note that if you want to distribute them separately, they will want to be in separate directory trees, each under a 'lib' directory in it's own package. So the quite often the normal way to work with these would be to have something like this:

MassSpec-LipcutElementsIO
    lib
       MassSpec
            LipcutElementsIO.pm

MassSpec-LipcutElementsIO-Search
    lib
       MassSpec
            LipcutElementsIO
                Search.pm

[download]

(Other expected directories and files omitted for clarity.)

So, that's actually an argument for both. (Which is how I develop.) When you want to upload to CPAN, you basically tar up the top-level directories above. (Although there are tools that will help make sure you are getting all the little details right.)

In reply to Re: code-controlled module naming conventions? by DStaal
in thread code-controlled module naming conventions? by jae_63

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.