What if I have a module that does something specific like Sports::Play::Tennis, but there is no Sports::Play- and I'm thinking there could be? A dangling module if you will..
I have a module that I placed in namespace Finance::MICR::LineParser. Thing is, Finance::MICR does not exist. It should/could exist- and my LineParser.pm module does not belong as MICR. I know it.
Another example, I have a module to manage metadata for files specifically for a website. It seemed like the right thing to do to name it as CGI::Metadata::Filed (i didn't think it belonged in Metadata, i thought this was more of a cgi thing then what is currently *in* the Metadata namespace). The reasoning is that there could/would/should be a CGI::Metadata::SomethingElsed.
When I have modules that sort of dangle like this.. Is this ok? Am I pissing anybody off? Should I just have called those CGI::MetadataFiled and Finance::MICRLineParser? Please suggest. I don't want to potentially pollute.
In reply to How to name modules without a parent namespace? by leocharre
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |