All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

Can you give a bit more info as to what use these two modules are? Looking at the source, all they do is store year/month/day/hour/min/sec and give one shortcut for printing those out.The docs make the excuse that loading time modules takes 3-4MB (only true for DateTime - try something lighter like Date::Class or Time::Piece), but for *::Tiny to do anything useful it looks like you'd have to do that anyway.

I (for obvious reasons) totally disagree with the flamebait in your docs about how DateTime.pm is the

I recently worked on an soft-realtime Perl application (using POE) that dealt heavily with dates and times. Not manipulating them, but they had to be parsed and potentially converted between formats.

What I found was that quite a significant amount of work was having to be done just to create the DateTime objects, far more than I was comfortable with.

And yet the data did not require that level of rigour, I wasn't going to be doing anything with the dates, just holding them in memory, possibly converting to a different format, and possible dumping them back out later in the same of a different format.

What I needed was an extremely light, very quick to parse, implementation of a simple data object for date/time/datetime that I could use when speed and lightness were essential.

But having something like that disconnected from DateTime entirely made things difficult for the two places I needed full DateTime logic, and compromised the concept.

Hence the light implementation, with a optional converter to a DateTime object.

I would expect these modules to be used in those scenarios, time-critical or speed-important applications, where no significant manipulation needs to be done, but you still want a sane object form for a date/time/datetime.

As for DateTime being the only module to get it "right", perhaps the term "comprehensive" is better. I've hit various limitations with various date and time modules over the years (and I've written one of my own, a fork of Time::Piece under a previous name) and I never felt they were comprehensive enough to be the One True Solution.

And after doing a lot of date and time work, I've eventually reached the opinion that DateTime is the Right approach to the problem.