![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png) simont |
Sat 2012-12-22 22:50 |
Ah, a particularly special Y2K / Y2038 / etc sort of problem? Could be :-)
(I think the previous best I'd seen was a Y1997 problem: a couple of years ago I used BeebEm to resurrect all the programs I'd written for BBC Masters and Econet at school, and discovered that the file server protocol's time format had had a 4-bit year field with an epoch of 1981. Oops. But it turned out that since the same protocol was reused by RISC OS, Acorn had updated it to turn a few unused bits into an extension of the year field, so I was able to fix that bug in my old programs and get them working again :-) |
|