Show quoted text> > Date::Parse should really
> > be Y2038-safe ...
>
> Why?
Because time does not suddenly stop in the year 2038? Because people
might want to deal with dates that far away? Because time_t is not
magically 32 bits? Sorry, but you sound a bit like "I don't need four
digit years" in 1999 ...
Even if you really think that you have a valid point for some reason,
Date::Parse should at least warn when using larger dates or mention
it in the documentation.
Show quoted text> If it does not fit your needs, then I suggest looking at the
> DateTime modules
Done, I have switched our project to DateTime::Format::DateParse,
which I can recommend as an alternative to those who want to deal
with dates in the future ...
str2time() can be replaced by
DateTime::Format::DateParse->parse_datetime($date, [$timezone])->epoch()
Cheers,
Alex