I have just released the module Date::Object, that in the first view is an alternative to DateTime, at least for the most common things when handling dates.
http://search.cpan.org/~gmpassos/Date-Object-0.01/ The main pourpose is to handle dates using a single object or make multiple "Date::Object"s work together to calculate and handle dates. Other main poupose of Date::Object is to find a simple way to store dates in a persistent enverioment (any database) using a simple INTEGER field. The use of a INTEGER field for that make possible searches in the DB by ranges, what is impossible with normal storages of dates, specially if they are saved as STRING, generally in the comon format of "YYYY-MM-DD". Also an INTEGER field have all the informations of a date, including year, month, day, hour, minute, second and timezone. Other good thing is that any DB supports INTEGER fields, what doesn't make our Perl code dependent of the SQL nuances of each different way to handle dates of each DB. Internally Date::Object has a simple architecture and is small compared to other Date modules, since all is based in the time() (all the seconds from 1970-1-1) of the object. Soo, each object has it's own time value and timezone, and from this 2 values any information is calculated. Soo, change only 2 values make all the work easier to create the module and move the date through the timeline, and with simple methods is possible to add/remove days, weeks, months, years, and make comparations. As any other author that releases a new module, I'm asking for some feedback about the module. Thanks in advance. Regards, Graciliano M. P.
