Y2K38 Problem...

:: Year 2038 Problem
Source:
http://en.wikipedia.org/wiki/Year_2038_problem



The year 2038 problem (also known as "Unix Millennium bug", "Y2K38," "Y2K+38," or "Y2.038K" by analogy to the Y2K problem) may cause some computer software to fail before or in the year 2038. The problem affects Unix-like operating systems, which represent system time as the number of seconds (ignoring leap seconds) since January 1, 1970. This representation also affects software written for most other operating systems because of the broad deployment of C. On most 32-bit systems, the time_t data type used to store this second count is a signed 32-bit integer. The latest time that can be represented in this format, following the POSIX standard, is 03:14:07 UTC on Tuesday, January 19, 2038. Times beyond this moment will "wrap around" and be represented internally as a negative number, and cause programs to fail, since they will see these times not as being in 2038 but rather in 1901. Erroneous calculations and decisions may therefore result.

음...
time_t 를 unsigned 32-bit integer로 바꿔도 year 2106 밖엔 되지 않군요...
하아~ 순간 OS 에 상관없이 64bit 로 슬슬 준비 해야할까? 라고 생각했는데,,,
과연 내가 2100 年 까지 살수나 있을라나 ? :)

죽기전에 나의 DNA 와 뇌의 모든 정보를 backup 해서 Matrix 에 넣어줬으면 좋겠다...

Cheers,
godmode2k