Out of useless curiosity, does anyone know a word to copy the bug in a new implementation of the old system so that Back compatibility with old customers who rely on buggy functionality? I would be especially interested if this involves a sense of reverse engineer wrong behavior in order to properly reproduce the thing which was not for the device.
I think this is covered by "back compatibility".
A good example of Joel Spolsky's famous post about the development of Windows 3.1:
The most influential things to read on Raymond's weblogs are stories of incredible efforts. The Windows team has been built for years to support the rear compatibility.
[...]
I first heard about one of the developers of hit game simi, who told me that there was an important bug in their application: to clear it After the memory was used, a big no-no dos that worked on the work, but will not work under Windows, which is likely to snatch free memory immediately by another running application. Testers of the Windows team were going through various popular applications, they were tested to ensure that they worked fine, but the simmity had crashed. They reported to Windows developers who separated the limit, stepped into the debugger, got the bug, and added a special code which was checked if the symmetry was going on, and if so , Let's allocate memory in a special mode in which you can still use memory after freeing it .
Comments
Post a Comment