This article needs additional citations for verification. (February 2013) (Learn how and when to remove this template message)
Legacy code is source code that relates to a no-longer supported or manufactured operating system or other computer technology. The term was first used by computer scientist George Olivetti to describe code maintained by an administrator that did not develop the code. The term can also mean code inserted into modern software for the purpose of maintaining an older or previously supported feature – for example supporting a serial interface even though many modern systems do not have a serial port. It may also be in the form of supporting older file formats that may have been encoding in non-ASCII characters, such as EBCDIC.
In practice, most source code has some dependency on the platform for which it is designed – even if a programmer uses a platform-independent programming language like Java, it is hard to write a large, useful program that is totally independent of its environment. When the manufacturer upgrades a platform (or the platform is superseded), the code may no longer work without changes, and becomes legacy code. A large part of the task of a software engineer is to continually alter code to prevent this.
While the term usually refers to source code, it can also apply to executable code that no longer runs on a later version of a system, or requires a compatibility layer to do so. An example would be a classic Macintosh application which will not run natively on Mac OS X, but runs inside the Classic environment, or a Win16 application running on Windows XP using the Windows on Windows feature in XP.
More recently, the software engineering community has developed other interpretations for the term legacy code. Among the most prevalent are source code inherited from someone else and source code inherited from an older version of the software. Michael Feathers introduced a definition of legacy code as code without tests, which reflects the perspective of legacy code being difficult to work with in part due to a lack of automated regression tests. He also defined characterization tests to start putting legacy code under test.
- Samuel Mullen 'Legacy isn't a Bad Word' (http://samuelmullen.com/articles/legacy_isnt_a_bad_word/)
- Michael Feathers' Working Effectively with Legacy Code (ISBN 0-13-117705-2)
|This programming-language-related article is a stub. You can help Wikipedia by expanding it.|