Re: Registering CPAN module namespace

[andreas1234567]

You mean this post is yours? Like you said it got a response, which seemingly remains unanswered.

From what I understand you wrote a variant of Time::HiRes and you want to call it RHP::Timer where RHP is what you call yourself on the internet. Naming a CPAN module after who wrote it both undescriptive and confusing. A little searching brought me here:

2.5 Select a name for the module.

This name should be as descriptive, accurate and complete as possible. Avoid any risk of ambiguity. Always try to use two or more whole words. Generally the name should reflect what is special about what the module does rather than how it does it.

I suggest you spend some time finding a better name for your module, and then post again on [e-mail]. How about Time::HiRes::Simple?

[redhotpenguin]

I thought about using a subset of the Time::HiRes namespace, but at the time I wrote the module it was really for my specific needs and I wasn't sure if it was worthy of the Time::HiRes namespace :)

I've seen arguments flare up before in cases like that (i.e. Tiny), so I decided to take what I thought was the safe route and give it a namespace indicating it was something built for my custom needs rather than general usage - figured that if it gained any traction I could always rename it under the T::H namespace.

[leocharre]

This sounds personal. I too have my own personal customized fluffy pillow code. I have a good bit of it, actually. Class, Class2, CLI, DEBUG, Dev...

If I know in my little heart that the code is so specified, so me, so... That I just drop it under my own personal non registered namespace.
I use my cpan handle as my top level namespace. And I don't ask to register the name with cpan. Having a personal, 'yourcode' module and registering the namespace on cpan is an oxymoron. The whole idea of putting stuff up there is so others can use it. If you have something 'you'- then others can't really directly use it, or wouldn't choose to, would they? That doesn't sound like module stuff, that sounds like script implementation level material- or config file realm.

If you have customizations, maybe it should be controlled by a script or config file instead- to be worthy of a cpan namespace registration.

I'm not entirely sure why brian d foy and others put up with people like me posting quasi-junk such as 'personal'-ish code.

Maybe in hopes that it's actually helpful in other things we do that would very much be used by others.

I use my CPANHANDLE:: modules in projects others may use. But I am not presumptive to imagine other developers would want to use my variations of Getopt::Std - ones that hard code that the option flag '-d' means debug is on.

I think it's pretty safe to drop it under your cpan handle, who else would want to use an ugly ass namespace like LEOCHARRE:: to register stuff in. (PHRED actually sounds kinda coooool.. maybe I'll write a namespace suggestion module and name it PHRED, and register it on cpan.)

(I hope you don't feel proprietary over the namespace, as in it should be signed by me, that would be childish. Just write your name twice in the AUTHOR pod section instead! :-)

Hope some of that helps.