in reply to Designing Multifile Modules

One thing that may help you is to realise that there is nothing that say that Some::Module::A has to have any specific relationship to Some::Module or Some::Module::B. Any one of these could be a parent, sibling or child, or completely unrelated to either of the other two.

Whilst it can be helpful to have the naming and directory structures reflect the hierarchy of classes, it can introduce some inconvenience also.

A possible approach to the problem would be to name your classes something along the lines of 

Our::ProjectA::Doobries
Our::ProjectA::Thingumajigs
Our::ProjectA::Wotsits
Our::ProjectB::These
Our::ProjectB::Those
Our::ProjectB::AndThemToo

[download]

Ie. Just stick with a flat namespace within the project regardless of the class hierarchy.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.

In Section Seekers of Perl Wisdom