I am having just as much trouble figuring out what your question is as you are having trouble writing said question!

A project for me may have say 15 project specific modules. I think this is on the order of your project? I think up a TLA (Three Letter Acronynm), like "TDP", "This Darned Project" that describes the project. I use that capitailzed TLA in all file and package names related to the project.

I make a directory like "../TDP/TDP_LIB". The source code (.pl) programs go into ".../TDP". All of the .pm modules for that project go into ".../TDP/TDP_LIB". I name all of the .pm module file names with a name like: "TDP_parsing.pm". That same file name is used within the .pm module as the package name: package TDP_parsing;

A program that uses project specific parsing from TDP, might code as:

uselib "../TDP/TDP_LIB"; #some path to TDP project specific modules use TDP_parsing;
I haven't used the double colon, "::" for paths and package names. All of my packages have an "O/S legal" file name. I usually make the package name to be the same as the O/S name for that file. A package name like "pm::abc" does not meet that requirement. I personally would make that "PM_ABC" because it eliminates one level of directories.

In summary, there does appear to be some ambiguity when using the double colon "::".


In reply to Re: Module's name and file's name by Marshall
in thread Module's name and file's name by beurive.denis

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.