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 sinc

Re: Module name hierarchy...

On Wednesday, 30 September 2020 07:55:40 CEST BC wrote: > I can avoid the whole problem by > just picking a different but similar name: > > Class::Fault > > which is currently not used. For my purposes that name works well. > The only thing I don't like is that it feels like I am squatting o

Re: Module name hierarchy...

On Wed, Sep 30, 2020 at 1:56 AM BC wrote: > The only thing I don't like is that it feels like I am squatting on > something fairly generic near the top of the name space. If I were to > push my one and only module down a level as: > > Class::Fault::Foobar > > would it be a faux pas if there

Re: Module name hierarchy...

Thanks to John, David, and Dan for their thoughts on my module naming question. So to avoid potentially tromping on another author's name space doing something like: Class::Error::Foobar where `Class::Error` already exists, I can avoid the whole problem by just picking a different but simila

Re: Module name hierarchy...

On Fri, September 25, 2020 4:12 pm, David Cantrell wrote: > On 25/09/2020 19:59, Dan Book wrote: >> On Fri, Sep 25, 2020 at 2:20 PM BC > > wrote: >> >> Let's say I wanted to submit a module named: >> >>      Class::Error::Foobar >> >> Would this be

Re: Module name hierarchy...

On 25/09/2020 19:59, Dan Book wrote: On Fri, Sep 25, 2020 at 2:20 PM BC > wrote: Let's say I wanted to submit a module named:      Class::Error::Foobar Would this be considered bad form if my "Foobar" module is not related to the existing Clas

Re: Module name hierarchy...

On Fri, Sep 25, 2020 at 2:20 PM BC wrote: > Let's say I wanted to submit a module named: > > Class::Error::Foobar > > Would this be considered bad form if my "Foobar" module is not related > to the existing Class::Error module in any way? In other words, > Foobar does not depend on, extend,