I understand your point, however, this is not a calendar and does not
produce one yet. Sure I would like to have it create a calendar where you
say my fiscal year starts 03-01 and I have 13 periods and it produces a
calendar view of the year with 13 periods of 28 days, so Mar 29 - 31
appeared in the second period if that is the way you want it. We are not
there yet. I went with this name so I had a package namespace, I am not
stuck on it, but it seemed like if I waited to start till we had a name
everone agreed on, then there might be a few more leap seconds before this
sort of thing ever got going.
"Have a name before you start programming ..."
- Ingy YAPC::2003
On 22 Jun 2003, [ISO-8859-1] Claus F�rber wrote:
> Jesse Shy <[EMAIL PROTECTED]> schrieb/wrote:
> > OK , I am coding up the port from Date::Calc::Fiscal right now. I should
> > have something for y'all to look at by the end of the day ( I hope ). I
> > will still have to write docs and test.
>
> I see two problems with the name:
>
> * it introduces two new levels, it would be the only module under
> DateTime::Fiscal::*
> * it seems to belong into DateTime::Calendar::*, not into an own
> namespace directly under DateTime::*
>
> Maybe DateTime::Calendar::Fiscal?
>
> Claus
> --
> http://www.faerber.muc.de
>
