On Fri 2003/03/21 19:46:22 CST, Dave Rolsky <[EMAIL PROTECTED]> writes: > So we might have a DateTime::Recurrence::EveryX module that had stuff like > "every month", "every year", "every quarter", etc. And there could be a > DateTime::Recurrence::CatholicHolidays module, which internally might use > things like DateTime::Event::Easter, DateTime::Event::Christmas, etc.
Events should be unambiguous. It's been a while since I did alot with different calendars, but I know there are 2 (3?) different algorithms for Easter and some other "common" holidays are not unambiguous (can't remember what I ran into off-hand). Alternately, DateTime::Event::Easter (and similar modules) could contain all of the algorithms for calculating a given event (you just pass different constructor arguments or call different functions or something). > I'm not sure I actually like the particular namespace > DateTime::Recurrence, but obviously DateTime::Calendar is not available. > Other possibilities might be > > - DateTime::Events (easily confused with DateTime::Event, though) > - DateTime::EventSet > - DateTime::PredefinedSet > - DateTime::SetLibrary > > Other suggestions are welcome. I don't like DateTime::Recurrence either. Ideal (to me) would have been DateTime::Calendar. Of the ones above, I think I like DateTime::EventSet - it clearly gives an idea of what it is (a pre-packaged set of events).
