Module Naming

Spidy has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: Module Naming by dragonchild (Archbishop) on Nov 11, 2007 at 01:42 UTC
Put it under DateTime:: - call it DateTime::NaturalLanguage and release DateTime::NaturalLanguage::EN with it and allow someone to come along and create DateTime::NaturalLanguage::CN or ::FR or whatever. My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]
Re^2: Module Naming by Spidy (Chaplain) on Nov 11, 2007 at 04:48 UTC
I think that this is the best idea thus far - but I'm a little confused. How exactly would I go about releasing DateTime::NaturalLanguages and DateTime::NaturalLanguages::EN with it? Would I just release the two modules (both in english), and then mention in my POD that if anyone wanted to translate it they were free to? website army	[reply]
Re^3: Module Naming by dragonchild (Archbishop) on Nov 11, 2007 at 04:51 UTC
Release one distribution called DT::NL and have it bundle DT::NL and DT::NL::EN. That will be the default choice, but you might want to look at whatever localization ENV there might be. Or, just let the user set it. DT::NL will create and return a DT::NL::EN - it will be a factory. You mention in the POD for DT::NL that there is a mechanism for providing different languages and point to DT::NL::EN as a reference implementation. Then, you don't do anything else and let people release versions as they see fit. As they do, you will get requests for new features or to reorganize the code in such a way as to make their lives easier. Be responsive and you just created a community around your little module. My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]
Re^2: Module Naming by CountZero (Bishop) on Nov 11, 2007 at 18:32 UTC
Unless the module provides a standard "DateTime" object somehow, it would be confusing to put it under the "DateTime"-namespace. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James	[reply]
Re: Module Naming by Fletch (Bishop) on Nov 11, 2007 at 02:31 UTC
Sounds similar to DateTime::Format::Duration . . . We're looking for a Perl and Database Developer for Corporate Investments Group.	[reply]
Re^2: Module Naming by Spidy (Chaplain) on Nov 11, 2007 at 04:46 UTC
Similar, but not quite the same - while DateTime::Format::Duration takes a hash as arguments, this module would be taking a number of seconds - which it would then convert into the respective values. website army	[reply]
Re^3: Module Naming by McDarren (Abbot) on Nov 11, 2007 at 05:50 UTC
hmm, this sounds like it is almost exactly what I was looking for a couple of years ago.... I'd be interested to see your code, and how it compares to some of the methods offered in that thread.	[reply]
Re: Module Naming by Popcorn Dave (Abbot) on Nov 11, 2007 at 04:43 UTC
What about Time::Abstract or Time::English? Revolution. Today, 3 O'Clock. Meet behind the monkey bars. I would love to change the world, but they won't give me the source code	[reply]
Re: Module Naming by diotalevi (Canon) on Nov 11, 2007 at 06:42 UTC
It sounds like a Lingua::EN::Duration to me. ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊	[reply]
Re: Module Naming by jdporter (Paladin) on Nov 11, 2007 at 14:39 UTC
`"3 years, 28 months"`? That doesn't look very useful to me. ;-) Anyway, perhaps these: Time::Elapsed Time::Duration Time::Seconds If not, then you could consider following the pattern set by other modules which similarly do formatting of numbers: Number::Spell Lingua::EN::Numbers Lingua::EN::Num2Word :-)	[reply] [d/l]