Facebook
Google
GitHub
Linkedin
Year 2038 problem.
- Thread starter bertus
- Start date
schmitt trigger
- Joined Jul 12, 2010
- 2,027
I hope that it will be another non-event like the Y2K bug.
Oh God, not again! I spent countless hours doing "Due Diligence" last time. Identifying every control system that had a clock in a huge chemical refinery. Getting Certificates of Compliance from every manufacturer identified. Had to be On Site for New Years Eve and visit every control room to verify no hiccups in operations. What an absolute waste of time and money. A lawyers dream job!
For the life of me, I can't understand how such dumb decisions could be made. They did the same thing for memory. Why used a signed variable when a negative quantity didn't make sense?
Gonna have to brush up on my COBOL/CICS again.
You can't fix stupid. Sensible systems and codebases have used 64-bit integer to hold Unix time for a long time.
The problem is utterly trivia, with known solutions and fixes in general use for a long time.
If you're alive in 2038 and get bit by this on some ancient W95 era system still in use, count yourself as lucky as hell on both conditions.
The problem is utterly trivia, with known solutions and fixes in general use for a long time.
If you're alive in 2038 and get bit by this on some ancient W95 era system still in use, count yourself as lucky as hell on both conditions.
