I'm adapting Strptime to return DateTime::Incomplete objects when it
gets an incomplete datetime. The old behaviour was to return the lowest
possible value.
eg. 'November 2003' used to return 2003-11-01T00:00:00, but will now
return 2003-11-xxTxx:xx:xx
I'm currently checking to see if a
David Hood [EMAIL PROTECTED] wrote:
Perhaps you should return only the information that
is given, in an
iso 8601
compliant format, so for November 2003 you could
simply return
2003-11. The
Nah, that's not going to happen. The entire point of
the module is to get a DateTime object.
Rick Measham wrote:
I'm adapting Strptime to return DateTime::Incomplete objects when it
gets an incomplete datetime. The old behaviour was to return the lowest
possible value.
eg. 'November 2003' used to return 2003-11-01T00:00:00, but will now
return 2003-11-xxTxx:xx:xx
I'm currently
Hi All,
I was just wondering if anyone on the list is planning to attend
Comdex/Apachecon 2003?
Ron Hill
Dave Rolsky wrote:
On Mon, 3 Nov 2003, Flavio S. Glock wrote:
I'm working on a fix.
I just checked in a fix.
Flavio S. Glock wrote:
Fixed:
And I made yet another fix to make the CVS fix equal to the CPAN fix :)
I guess we are done with fixes today.
- Flavio S. Glock
Rick Measham wrote:
If so, maybe a method inside Incomplete would be good:
if ($dti-can_be_datetime) {
$dti-become_datetime
}
I've put this in the TODO.
So this is the current list of proposed DT::Incomplete methods that are
waiting for votes:
* epoch
$epoch = $dti-epoch
$span = $dti-span;
I really like the idea of being able to measure the uncertainty in an object. What if
the year and day are known but not the month? Would a span set be returned?
-J
--
