Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

Your current structure sounds fine to me.

I think people will believe that B, C and D are inheriting A and not composing it.

If, as you say, B, C and D are only ever used by A then the casual user probably won't even consider that they exist. Anyone after more than that will read the documentation and so long as that is clear there should be no confusion.

What is the currently considered a best practices for module organization and naming when it comes to composition?

I don't know that there is really a set of best practices for that specifically. If in doubt, go for clarity (which is again in the eye of the beholder). If you have specifics (ie. the actual proposed names) then you can ask here or on PrePAN.

In reply to Re: Perl modules hierarchy and composition by hippo
in thread Perl modules hierarchy and composition by tusker

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.