Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation

Re: Perl modules hierarchy and composition

by hippo (Bishop)
on Jan 06, 2017 at 06:20 UTC ( #1179072=note: print w/replies, xml ) Need Help??

in reply to Perl modules hierarchy and composition

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.

  • Comment on Re: Perl modules hierarchy and composition

Replies are listed 'Best First'.
Re^2: Perl modules hierarchy and composition
by tusker (Novice) on Jan 06, 2017 at 06:39 UTC
    Thanks! Your answer converges with other advices I got. But there is never enough wisdom, so I wanted the monks advice.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1179072]
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others taking refuge in the Monastery: (5)
As of 2023-11-29 11:04 GMT
Find Nodes?
    Voting Booth?

    No recent polls found