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
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