Linked by Thom Holwerda on Fri 17th Nov 2017 11:51 UTC

Really, quite literally, some pretty skilled Microsoft employee or contractor reverse engineered our friend EQNEDT32.EXE, located the flawed code, and corrected it by manually overwriting existing instructions with better ones (making sure to only use the space previously occupied by original instructions).

This... This is one hell of a story. The unanswered question is why, exactly, Microsoft felt the need to do this - do they no longer have access to the source code? Has it simply become impossible to set up the correct build environment?


Permalink for comment 651052
To read all comments associated with this story, please click here.
Member since:

Most of the incompatibilities I have seen from old C code, and I have had to deal with ancient code bases at some jobs were mainly due to architectural assumptions. Other than that most of the old C code I'be seen it's pretty portable, there was not that much to the language after all.

Reply Parent Score: 4