On Sun, 3 Jun 2001 00:16:09 -0400 (EDT), srl said:
> So, I notice that in the new Date::ICal module, the new() function
> behaves like so:
>
> $t = new Date::ICal (epoch => 123456); # epoch seconds
> # OR
> $t = new Date::ICal (ical => '20010304T103000Z'); # an iCalendar date
>
> I know that not all systems have the same epoch; hence, if I create
> a new Date::ICal with (epoch => 0), I'm going to get different times
> depending on the platform. I have to create times with iCalendar
> in order to get correct date/times.
>
> Anyone have suggestions for how to handle this? Perhaps there
> should be some conditional code in the make process that determines
> the platform and causes the code to behave sanely there?
I thought about this when I was writing it, and I hoped to solve it by the
advanced technique called "hoping nobody notices." Actually, Chris Nandor has
already made a note that we need to be aware of this sort of thing, and I was
hoping to get a release out there, and then tackle this next. However, you're
right, I'm not sure how to find out when a particular machine's epoch is. I
expect, however, that looking at Date::Calc or Date::Manip, and seeing how they
handle it, will be my first approach.
--
Pilgrim, how you journey on the road you chose
To find out where the winds die and where the stories go
--Pilgrim (Enya - A Day Without Rain)