Skip Menu |

This queue is for tickets about the Date-Manip CPAN distribution.

Report information
The Basics
Id: 78413
Status: resolved
Priority: 0/
Queue: Date-Manip

People
Owner: Nobody in particular
Requestors: chris [...] theclonchs.com
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 6.32
Fixed in: (no value)



Subject: Sub second support
Show quoted text
> As a supporting piece of evidence of this... in the 15 years since > Date::Manip was released, you're only the 2nd person to request support > for fractional seconds. So I don't see it as being 'severly limiting'.
Just to make my voice heard, I would really like to see support for sub-seconds! I just finished writing a script to organize digital photographs by date, which of course uses Date::Manip. Once completed I realized that most new digital cameras store sub-second information in the EXIF metadata, particularly if they offer a sports, or rapid shutter fire, mode. This is needed as the camera captures several pictures per second. Now I'm faced with re-writing the script using the other various date/time modules. Obviously it is easier for me to do this than for you to invest the considerable amount of time it will take to add in support to the module. But I really see value in it, and the value others will gain by Date::Manip supporting it. Thanks, -Chris
I am considering this request, but there are a few factors that make this a very low priority right now: 1) I've received this request twice in the 16+ years Date::Manip has been around. It's a feature that very few people need or care about. 2) Modifying the seconds will actually impact a lot of different parts of Date::Manip. It'll mean changing the parsing and date calculation code at the very least, and that's a huge chunk of Date::Manip . In other places, it may not require significant changes... but it will require a complete audit of all of the code. At this particular moment, I'm pretty busy with other projects and don't foresee spending the time to add this feature in the near future. Further along... it's a possibility, but as a general rule, I do prefer to spend my time on the features that give the highest return (i.e. usefulness) per time spent, and unfortunately, I perceive that ratio to be really small for this feature (i.e. a lot of time to implement, very low return), and that perception hasn't changed over the years. You're free to try to change my perception of that of course, but even so, that won't change the fact that I don't have time to do a full audit of Date::Manip in the near future. So, I guess what I'm saying is that if your project won't work (as written) until Date::Manip is fixed or your project is rewritten (at least in part), your fastest time to completion will definitely be the 2nd option. Sorry about that. Now, it may not really require that, depending on how you use Date::Manip... you might be able to just keep track of the fractional seconds yourself and not require a full rewrite, but I don't know, having not seen how you are using Date::Manip .
All that being said, I am going to spend a little time and try to determine just how much work it would be. If it turns out that it's not TOO much work, I'll add it to my TODO list.
From: chris [...] theclonchs.com
On Tue Jul 17 09:24:33 2012, SBECK wrote: Show quoted text
> All that being said, I am going to spend a little time and try to > determine just how much work it would be. If it turns out that it's not > TOO much work, I'll add it to my TODO list.
I would really appreciate it! And I can also appreciate the amount of time it can take to cut in such a feature. And just let me thank you for the work you've already put into the module! Thanks again, -Chris
Closing out an old ticket. This is really a 'wishlist' item, not a bug, so it's being considered for a future release, but no promise or timeline at this time.