Computing.Net > Forums > Programming > Year 2038 Problem

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Year 2038 Problem

Reply to Message Icon

Name: Dr. Nick
Date: September 14, 2003 at 23:58:42 Pacific
OS: WinXP Pro SP1
CPU/Ram: P4 2.0Ghz & 1024MB pc133
Comment:

Hey, how many of you guys knew about this? Pretty interesting, especially if you understand the article (remember, there's only 10 kind of people in the world. Those that understand binary and those that don't.)

http://pw1.netcom.com/~rogermw/Y2038.html



Sponsored Link
Ads by Google

Response Number 1
Name: Jake
Date: September 15, 2003 at 09:17:33 Pacific
Reply:

I know because I recently wrote a PERL script for UNIX that uses a few time/date functions. For example, it compares date/times as seconds since the epoch, 1/1/1970. I'm sure my 500 line script will be obsolete by 2038, so I'm not worried.


0

Response Number 2
Name: Dr. Nick
Date: September 15, 2003 at 10:57:19 Pacific
Reply:

Very true, though the author does make some interesting points.

As a side note, I set my Windows clock to the year 2050 and two applications that were running in the background crashed within about 20 seconds.


0

Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Programming Forum Home


Sponsored links

Ads by Google


Results for: Year 2038 Problem

COBOL programs www.computing.net/answers/programming/cobol-programs/13474.html

problem with date() function in PHP www.computing.net/answers/programming/problem-with-date-function-in-php/8855.html

Batch/VC++ choice problem www.computing.net/answers/programming/batchvc-choice-problem/9057.html