|This article needs additional citations for verification. (March 2010)|
An aspect of maintaining backward compatibility with an older system is that such systems' client programs often do not only depend on their specified interfaces, but also on bugs and unintended behaviour. This must also be preserved by the newer replacement. Besides the significantly higher complexity that needs to be maintained during the natural evolution of the code or interface, this can sometimes cause performance or security issues, and the inconsistencies in the behaviour of interfaces can sometimes led to new bugs in the software using it, creating difficult to resolve multi-directional cross dependencies between various pieces of code.
Examples of this can be found in MS-DOS / PC DOS, where the executable loader contains code specially designed to detect and fix a number of widespread bugs in applications and runtime libraries by patching the loaded image before executing it. Over the course of development, DR-DOS also had to be modified to not only emulate many undocumented peculiarities of MS-DOS / PC DOS, but also actual bugs in the kernel and several drivers in order to make certain other drivers and applications run on DR-DOS, when they were tested on specific versions of MS-DOS only.
Windows, which has traditionally emulated many old system bugs in order to allow older low-level programs to run, is another example. As a result, Wine, which makes it possible to run many Windows applications on other platforms, also needs to maintain bug compatibility with Windows.
- "Bug-compatible - www.jargon.net". Retrieved 2010-02-03.
- Matthias Paul (2002-02-20). "Need DOS 6.22 (Not OEM)". alt.msdos.programmer. Retrieved 2006-10-14.
- "WineFeatures - The Official Wine Wiki". Retrieved 2010-02-03.
|This operating system–related article is a stub. You can help Wikipedia by expanding it.|