Linked by David Adams on Thu 1st Mar 2012 22:53 UTC, submitted by judgen
Thread beginning with comment 509234
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2011-01-28
Everyone assumed that "Y2K" trouble was only about the year 2000, but most computers actually had different date boundaries.
The year 2000 was only a problem for those who stored dates in ascii/ebsdic form. Mainframes seem to be unusual in their use of BCD and nine's complement within their vsam files, which is why they were especially susceptible to the two digit overflow.
Binary time representations such as those in *nix have different limits, but they're also approaching.
http://en.wikipedia.org/wiki/Year_2038_problem