Source-code compatibility: Difference between revisions
imported>Arachinid replaced w10 with w11 |
imported>DreamRimmer bot II m Bot: Implementing outcome of RfC: converting list-defined references from {{reflist|refs=…}} to <references>…</references> for VisualEditor compatibility |
||
| Line 12: | Line 12: | ||
== References == | == References == | ||
<references> | |||
<ref name="Baron Higbie 1992">{{cite book | <ref name="Baron Higbie 1992">{{cite book | ||
| last1 = Baron | | last1 = Baron | ||
| Line 52: | Line 53: | ||
| page = 17 | | page = 17 | ||
}}</ref> | }}</ref> | ||
</references> | |||
{{DEFAULTSORT:Source Code Compatibility}} | {{DEFAULTSORT:Source Code Compatibility}} | ||
Latest revision as of 10:03, 22 December 2025
Template:Short description Template:Use dmy dates Source-code compatibility (source-compatible) means that a program can run on computers (or operating systems), independently of binary-code compatibility and that the source code is needed for portability.[1]
The source code must be compiled before running, unless the computer used has an interpreter for the language at hand.[2] The term is also used for assembly language compatibility, where the source is a human-readable form of machine code that must be converted into numerical (i.e. executable) machine code by an assembler. This is different from binary-code compatibility, where no recompilation (or assembly) is needed.[3]
Source compatibility is a major issue in the developing of computer programs. For example, most Unix systems are source-compatible, as long as one uses only standard libraries. Microsoft Windows systems are source-compatible across one major family (the Windows NT family, from NT 3.1 through Windows 11, or the family that includes Windows 95, Windows 98, and Windows Me), with partial source compatibility between the two families.