(Reply-to set to -datetime list)
Chaim Frenkel writes:
> NT> Epoch seconds are a convenient representation for dates and times.
> NT> Varying epochs make it an unreliable representation when data are
> NT> shared. A consistent epoch would fix this.
>
> Sorry, I don't buy that. Not every program will be perl.
Bogus argument. This is a non-issue. I'm talking about it being
easy to run the same program on different platforms but share data.
Optimize for Perl.
> The only valid interchange would be to specify the date unambiguously,
> for example the ISO <mumble, help me Jarkko> YYYYMMDDHHMMSS.fff
This is good for comparison but bad for math. Epoch seconds are
good for both. That's why *I* use them. You can continue to use
ISO mumble and have it work for you. I'm not breaking your code.
There's also the issue that Perl code should (where practical) be
portable by default. Perl tries to cover up operating system
oddities. This is one oddity that can (and, I think, should) be
covered up.
Nat
