Backward compatibility

From Wikipedia, the free encyclopedia

Jump to: navigation, search
 This article needs additional citations for verification.
Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (June 2008)

In technology, for example in telecommunications and computing, a device or technology is said to be backwards compatible if it allows input generated by older devices. A standard, for example a data format or a communication protocol, is said to allow backward compatibility, if products designed for the new standard can receive, read, view or play older standards or formats.

This should not be confused with forward compatibility, which implies that old devices allow data formats generated by new or future devices, perhaps without supporting all new features. A standard supports forward compatibility if older product versions can receive, read, view or play the new standard.

For example, the introduction of FM stereo transmission, or color television, allowed backward compatibility since new receivers could receive mono or black-and-white signals generated by old transmitters. It also allowed forward compatibility, since old mono FM radio receivers and black-and-white TV sets still could receive a signal from a new transmitter.

In programming languages, backwards compatibility refers to the ability of a compiler for version N of the language to accept programs or data that worked under version N - 1.[1]

Contents

[edit] Alternate definition

In other contexts, a product or a technology is said to be backward compatible when it is able to take the place of an older product, by inter-operating with products, that were designed for the older product.[2][need quote]

[edit] Description

Backward compatibility is a relationship between two components, rather than being an attribute of just one of them. More generally, a new component is said to be backward compatible if it provides all of the functionality of the old component.

Backward compatibility is the special case of compatibility in which the new component has a direct historical ancestral relationship with the old component. If this special relationship does not exist then it not usually spoken of as "backward" compatibility but is instead just "compatible"—a consistent interface allowing interoperability between components and products that were each developed separately.

Data does nothing in the absence of an interpreter, so the notion of compatibility does not apply to document files, it only applies to software. In the case of a program that creates document files, a new version of that program ("v2") is said to be backward compatible with the old version of the program ("v1") when it can both read and write documents that work with v1. Everything that v1 could do must also be possible with v2, including saving documents that can be read by v1.

If a newer software version cannot save files that can be read by the older version, it is not backward compatible with the older version, although it may provide an irreversible upgrade capability for the old files. This situation has often been used strategically by software vendors to force customers to purchase upgrades since, over time, the number of data files usable by an old version diminishes at a rate proportional to the number of other customers that have upgraded.

Levels of compatibility vary. In software, binary compatibility and source compatibility are distinguishable. Binary compatibility means that programs can work correctly with the new version of this library without requiring recompilation. Source compatibility requires recompilation but no changes to the source code.

Many platforms rely on emulation, the simulation of an older platform in software, to achieve backward compatibility.

[edit] Compatibility checking

Approaches for checking compatibility between the client program and the server component include:

  • Check by version number;
  • Check by an interface definition language (IDL)
  • Check by just-in-time test runs (the client program gives some example inputs to the server component to see if the component returns the desired example outputs).

[edit] Examples

 This article or section may contain poor or irrelevant examples.
Articles should only contain pertinent examples.
Please improve the article or discuss proposed changes on the talk page.
You can edit the article to add more encyclopaedic text. See Wikipedia's guide to writing better articles for further suggestions.
  • PCI Express 2.0 is backwards compatible with PCI Express 1.1.
  • The NTSC colour broadcast system was engineered by RCA to be backward compatible with black-and-white television sets.
  • A computer system is backward compatible if it is able to work with software or accessories designed for the system it is meant to replace.
    • The IBM 7080 transistorized computer was backward compatible with all models of the IBM 705 vacuum tube computer.
    • The Atari 7800 is backward compatible with most Atari 2600 games.
    • The Commodore 128 is 99% backward compatible with Commodore 64 software and hardware.
    • The Game Boy Advance line (except the Game Boy Micro) is backward compatible with previous Game Boy systems, meaning all Game Boy and Game Boy Color titles are playable on this system (except Game Boy title Road Rash).
    • The Nintendo DS is backward compatible with Game Boy Advance games (except Mega Man Battle Network 4: Blue Moon Version) only in single-player mode, due to the system's lack of a GBA link cable port, but not the newly release Nintendo DSi which is not compatible with GBA games or any peripheral using the Slot 2, for example Guitar Hero: On Tour.
    • The PlayStation 2 is backward compatible with most of the original PlayStation library.
    • The PlayStation 3 is backward compatible with most PlayStation and PlayStation 2 games. This is provided by the inclusion of the original Emotion Engine chip that is built inside the PS2. This form of compatibility is only available to the first series of consoles that launched across North America, Japan, Hong Kong and Taiwan, the later launch of the system in many PAL areas (Europe, Oceania, Asia) lacked the chip provided in the original units and instead relied on software emulation (which greatly reduced the number of playable titles) for backwards compatibility. It was announced that future versions of the console in all areas will lack the Emotion Engine with the first use of this seen in the new 80GB model. Currently there are no models of the PlayStation 3 in production that are capable of playing PlayStation 2 games.
    • All of Intel x86 processors – Core 2, Core, Pentium 4, Pentium III, Pentium II, Pentium Pro, Pentium, 80486, 80386, 80286, 80186 and 8086 – are backward compatible with their predecessors, because they can execute programs written for an earlier processor.
    • The Mega Drive/Genesis is not backward compatible with the Master System, however, Master System controllers can be used with the Mega Drive.
    • The Xbox 360 is backward compatible with some Xbox games. This is achieved through emulation.
    • The Wii is backward compatible with all games from the previous Nintendo system, the Nintendo GameCube, due to it being based on the PowerPC, the same base as the latter. It is compatible with GameCube controllers and memory cards but not with other peripherals such as the Game Boy Player. Some games originally released for older consoles – the NES, SNES, Nintendo 64, Sega Genesis, Turbografx 16 and Neo Geo – are available to play on the Wii via emulation, however the Wii cannot be said to be backward compatible with these systems as the software in its original format (i.e. cartridges) cannot be used.
  • Other examples of backward-compatible software
    • Microsoft Windows contains application compatibility shims to make the platform compatible with most software from earlier 32-bit and 16-bit versions (e.g. Civilization (circa 1991, designed for Windows 3.0) running on Windows Vista). XP, Vista and Server x64 versions drop 16-bit support for reliability while maintaining 32-bit support.
    • Microsoft Word 2000 was backward compatible with Word 97 because it could read and write files in Word 97 format, with the understanding that features unique to Word 2000 would not appear in Word 97. Same applied to Word 2002 and Word 2003.
    • By adding the proper external hardware, many consoles can become backward compatible. This includes:
    • Several computer operating systems have various methods of running software originally designed for older versions or other OSes:
      • Windows NT and successors have various subsystems to run legacy applications. MS-DOS and Win16 subsystems (only on i386) can run some applications for those platforms, and it has an OS/2 subsystem for running CLI OS/2 applications.

[edit] See also

[edit] References

  1. ^ Michael Kay, XSLT 2.0 Programmer's Reference, Wiley Default, 2004 ISBN 0764569090, 9780764569098
  2. ^ Jeffrey Zeldman (2006). Designing with Web Standards, Peachpit Press. ISBN 0321385551. 
Retrieved from "http://en.wikipedia.org/wiki/Backward_compatibility"
Personal tools