Bug #105622 for Date-Manip: invalid dates accepted as valid

Thu Jul 02 12:20:53 2015 Vitaly.Shupak [...] deshaw.com - Ticket created

Subject:	invalid dates accepted as valid
Date:	Thu, 2 Jul 2015 16:20:32 +0000
To:	"'bug-Date-Manip [...] rt.cpan.org'" <bug-Date-Manip [...] rt.cpan.org>
From:	"Shupak, Vitaly" <Vitaly.Shupak [...] deshaw.com>

The latest version of Date::Manip (at least since 6.41) accepts dates that are not valid: 6.41, 6.50 $ perl -MDate::Manip -le '$m=UnixDate("20141301","%Y%m%d %H:%M:%S") or die("Invalid date\n");print $m;' 20160220 14:05:06 6.24 $ perl -MDate::Manip -le '$m=UnixDate("20141301","%Y%m%d %H:%M:%S") or die("Invalid date\n");print $m;' Invalid date Is this a bug? Thanks, Vitaly

Tue Jul 07 12:11:50 2015 sbeck [...] cpan.org - Correspondence added

It was a bug... but not in the way you are thinking. One of the formats tried when parsing a date is to treat it as a delta (i.e. 'in 2 days'). Unfortunately, a pure number (such as 20141301) is treated as a valid delta (equivalent to 'in 20141301 seconds'). So that's the date that is being parsed. There was a bug in the earlier version that wasn't correctly treating that as a delta that has since been fixed. If you were to use the Object Oriented functions, you could eliminate this problem: $obj = new Date::Manip::Date; $obj->parse("20141301","nodelta"); but the functional interface doesn't have that flexibility. However, in looking at it, it is very easy to add, so I've added the same functionality to ParseDate and ParseDateString, so you'll be able to go: ParseDate('20141301','nodelta') and get the result you're looking for. This will be in the next release.

Tue Jul 07 12:11:50 2015 The RT System itself - Status changed from 'new' to 'open'

Tue Jul 07 12:11:56 2015 sbeck [...] cpan.org - Status changed from 'open' to 'resolved'