BTW, I think DT::Event::Cron should really be a wrapper to DateTime::Event::Recurrence, if possible. This would make maintainance and testing simpler.
- Flavio S. Glock 2006/9/29, Dave Rolsky <[EMAIL PROTECTED]>:
On Fri, 29 Sep 2006, Adriano Ferreira wrote: > I am offering myself as a volunteer to rewrite DateTime::Cron::Simple > as requested by Adam Kennedy. If there is no objection, I am starting > to code and will return with something as soon as possible. > > The reference will be the API described in the POD documentation of > the module. I will try to gave a look at the code proposed at > > http://rt.cpan.org/Public/Bug/Display.html?id=8262 > > but no promises. As the module is quite simple, I think coding from > scratch will probably be reasonably fast. (And God knows if there > would rise more license issues with the code the ticket requestor > sent.) If you could work with the author of DateTime::Event::Cron, Matt Sisk, to determine what DT::Cron::Simple did, and how it differed from DT::Event::Cron, that'd be great. I'm hoping that we can just incorporate its functionality into DT::Event::Cron directly. That namespace wasn't really right. There's no need for a DT::Cron::* namespace, it belongs under DT::Event if it ends up as a separate module. -dave /*=================================================== VegGuide.Org www.BookIRead.com Your guide to all that's veg. My book blog ===================================================*/
