On Wed, 14 Jul 2004, Bruno Negr�o wrote: > > His code is completely redundant with the Time::Seconds module that comes > > with Time::Piece, however. > > Yes, my code is redundant with Time::Seconds. But in the Time::Seconds man > page I saw the following statement: > "Bugs > Currently the methods aren't as efficient as they could be, for reasons of > clarity. This is probably a bad idea." > > So, since those calculations were so simple to implement, i decided to do > it by myself. I could use Time::Seconds as a base for my calculations but i > didn't think it was necessary. > > Do you think this was a bad assumption from the standpoint of... hmm... i > dont know, some standpoint!!...
Basically, it's bad because it clutters CPAN. Check out my article on date/time modules for Perl: http://www.perl.com/pub/a/2003/03/13/datetime.html There are a ridiculous number of modules out there. Most of them are very limited in scope, which is ok, but their APIs are awkward to hook together because they're all developed in isolation. That sucks. Your module is yet another module covering more or less the same ground as other modules, with no attempt to make it play nice with anything else. What makes the datetime project stand out is that it aims to cover _all_ the possible datetime areas, and to provide a well thought out API for each module. This means that you can pick & choose the datetime modules you need, and know that if you need additional functionality later, you will be able to find a module that integrates well with your existing code. -dave /*======================= House Absolute Consulting www.houseabsolute.com =======================*/
