Compliant and complaint are very different words. You want the former.

I wonder what system has a problem beyond 2013. On some systems, 2038 is the problem date. Here's a Windows build emulating the unix time format:

>perl -wle"print scalar gmtime 0x7FFFFFFF"
Tue Jan 19 03:14:07 2038

>perl -wle"print scalar gmtime 0x80000000"
Use of uninitialized value in print at -e line 1.
[download]

Changes to go far beyond 2038 have recently been incorporated into blead (what will become 5.12) if not maint-5.10 (what will become 5.10.1)

Update: By the way, DateTime can manipulate any date, not just those representable by time

I wonder what system has a problem beyond 2013

Looking at some of the other advice that's being provided at that link (all of which is very much tongue-in-cheek), I'd say that *none* of them do.

Cheers,
Rob

For good reason it is called the "perliaq" ("Infrequently Asked Questions").

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

doh! Thanks

I would like to know whether it is right or invalid one.

Perl Humor

The Lighter Side of Perl Culture (Part I): Introduction

Just to be explicit... it is invalid. It is a joke.

The document is a joke, but the statement is not invalid at all. Perl has no problem with year 2013 (or 2014 or 2015 or...), and shortly, it won't have any problem with the year 2038 either.

Unless I'm missing something, it's fine today, if you have enough bits.

$ perl -wle"print scalar gmtime 0x7FFFFFFF"
Tue Jan 19 03:14:07 2038

$ perl -wle"print scalar gmtime 0x80000000"
Tue Jan 19 03:14:08 2038

$ perl -v

This is perl, v5.10.0 built for x86_64-linux
[download]