Re: Module name hierarchy...

Thanks to Dan for that superlative example and Domi who asked:

> ... provided your Class::Fault is relatively generic. I.e. can it be
> used by an unrelated module ?

The module will indeed be generic.  It will be yet another way to
solve the common problem of error handling and reporting.  So since
there is no requirement for each step in the path to be an existing
module, I will go with

    Class::Fault::Foobar

where 'Foobar' will be some sort of descriptive name that attempts to
succinctly identify the strategy or approach being used for handling
faults.

Many thanks to all who took time to reply.

...BC