in reply to code-controlled module naming conventions?

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.)

Replies are listed 'Best First'.
Re^2: code-controlled module naming conventions?
by Bloodnok (Vicar) on Jul 22, 2009 at 14:41 UTC
    ...you basically tar up the top-level directories... - or make tardist in the top level directory of each module.

    A user level that continues to overstate my experience :-))
[reply]
[d/l]

In Section Seekers of Perl Wisdom