On Thu, 5 Jul 2012, Jim Bacon wrote:
I would like the advice of the DT community at large as to what would be a good name for such a module and what namespace it should go in. On the surface one would say DT::Calendar, but the module would create dates for various events such as the start and end dates for fiscal periods and reporting dates as well as being able to answer questions such as "What fiscal period does a given holiday occur in?" This would suggest that DT::Event might be better. That said, because of the planned ability to change from one period to another by means of methods such as "next" and "previous" neither "Event" or "Calendar" might be appropriate as they seem to imply a static condition and this would be decidedly dynamic. This argues for keeping the new module in the "Fiscal" namespace with an appropriate name.
If the module is about giving a DateTime object for an event, like the "next year in this wack calendar system", then it's a DateTime::Event module.
If it provides an alternate system for defining dates (Whooping Day 47 of Frobnitz Month) then it's a DateTime::Calendar.
If doesn't fit into either API comfortably, just call it DateTimeX::Foo and come up with an API that you think best expresses the problems you're trying to solve.
-dave /*============================================================ http://VegGuide.org http://blog.urth.org Your guide to all that's veg House Absolute(ly Pointless) ============================================================*/
