On Tue, Aug 15, 2000 at 09:25:34AM -0700, Larry Wall wrote:
> [EMAIL PROTECTED] writes:
> : Yep. Or more generally "Standardize Perl on all platforms to one
> : common time epoch" and reccommend the Unix epoch since it's so
> : widespread. :-)
>
> Oh, gee, where's your sense of history? (As in creating our own. :-)
> Maybe we should invent our own epoch, like the year 2000. Or use a
> really standard one, like the year 0 AD (aka 1 BC).
>
> I have this horror that people will still be using 1970 as the epoch in
> the year 31,536.
I tend to thing this whole epoc thing is overblown.
Few people would know what this time was just by looking at it: 966421517
So what does it matter if that time was represented by another string
of digits? What difference does it _really_ make what epoc is used, so
long as it's fully integrated into the language and interfaces along
with appropriate conversions to other epocs?
I tend to think that perl time should not break when presented with
Larry's date of birth :-)
We also need to avoid the unixtime 2038 bug, one way or another..
Tim.
p.s. For reference, Oracle DATE type can handle all dates from January 1,
4712 BC to December 31, 4712 AD. Oracle also supports a very wide range
of date formats and can use one of several calendars (Arabic Hijrah,
English Hijrah, Gregorian, Japanese Imperial, Persian, ROC Official
(Republic of China) and Thai Buddha).
