I have deleted DateTime::Pregnancy from CPAN, I will probably re-release it as Date::Pregnancy
I will then look into whether I can contribute anything based on this module to the DateTime namespace, respecting APIs, namespace and implementing as OOP.
Suggestions will be sent to this mailing list before releasing anything to CPAN
Now its back to the drawing board :)
After thinking for a couple of days, seems a new sub-name space for calculations wouldn't be a bad thing. However I'd like to see some sort of generic API. Maybe:
$object = new DateTime::Calc::FooBar( start => $dt1 end => $dt2 %options );
$pregnancy = new DateTime::Calc::Pregnancy( start => $conception_dt, ); $birth_dt = $pregnancy->end;
$pregnancy = new DateTime::Calc::Pregnancy( end => $birth_dt, ); $conception_dt = $pregnancy->start;
Just my $0.02 again. However I'm keen to keep this in the DateTime namespace as it states that the dates and times it uses are the most accurate around. Put it in the Date:: namespace and I'd guess it used Date::Calc or Date::Manip or any one of a hundred other things that are around. I'm getting the feeling from many places that DateTime has a lot of respect in the perl community.
Dave, can you make a decision on this .. there doesn't seem to be anyone saying we shouldn't make some other namespace. Here's the suggestions:
- DateTimeX:: - DateTimex:: - DateTime::X:: - DateTime::Misc:: - DateTime::Calc::
Cheers! Rick
-- -------------------------------------------------------- There are 10 kinds of people: those that understand binary, and those that don't. -------------------------------------------------------- The day Microsoft makes something that doesn't suck is the day they start selling vacuum cleaners -------------------------------------------------------- "Write a wise proverb and your name will live forever." -- Anonymous --------------------------------------------------------
