in reply to Re: Windows, Time::Local and dates before the epoch
in thread Windows, Time::Local and dates before the epoch

You mean write yet another Date/Time module that does more or less the same as the others. I'd be hung, drawn and quartered :)

I didn't want to write another module, simply because DateTime and Date::ICal are both well supported modules. If someone using my module wants reliable handling of dates then they are advised to install a reliable date handling module. Time::Local is the fallback simply because its in the Core.

Since yesterday I'm thinking along the same lines as Time::Local tests. If the user is happy with the boundaries set by Time::Local and localtime, then I don't really need tests that look beyond that. If they want to go beyond those boundaries then they should really install a more reliable date handling module.

I just found it infuriating having done all these tests and got it working on Linux, when I test it on Windows all these messages suddenly appeared. Such is life.

--
Barbie | Birmingham Perl Mongers | http://birmingham.pm.org/

  • Comment on Re: Re: Windows, Time::Local and dates before the epoch

Replies are listed 'Best First'.
Re: Re: Re: Windows, Time::Local and dates before the epoch
by Skeeve (Parson) on Jun 12, 2003 at 13:17 UTC
    You mean write yet another Date/Time module that does more or less the same as the others. I'd be hung, drawn and quartered :)

    I know. They did it to me after posting my reply. Downvoted almost instantly ;-)

    Nevertheless. If it's just a small routine, I prefer to use my own algorithm in favour of using just another library that need to be installed and that I need to learn to handle ;-)

    If someone using my module wants reliable handling of dates then they are advised to install a reliable date handling module

    That's fair and if you can live with it... okay for me :-)

    Maybe I will get hanged. I will try and write YADCM (Yet Another Date Calculation Module).