Reading more and more about Perl, I'm having doubts about how I organized my modules on my current project.
I have a main namespace - let's call it "MyProject". I have objects from class A that are composed of objects of class B, C and D. Classes B, C and D are used by class A only, so it made sense to me to organize the modules as follows:
- MyProject::A
- MyProject::A::B
- MyProject::A::C
- MyProject::A::D
But I'm starting to think that it will make sense to me only if I ever dare to relase parts of my project in CPAN. I think people will believe that B, C and D are inheriting A and not composing it.
So: shall I reorganize my modules this way?
- MyProject::A
- MyProject::B
- MyProject::C
- MyProject::D
Or maybe indicate that B, C and D are parts of A by appending their names?
- MyProject::A
- MyProject::AB
- MyProject::AC
- MyProject::AD
My question: What is the currently considered a best practices for module organization and naming when it comes to composition?
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.