Content deleted Content added
m Task 18 (cosmetic): eval 8 templates: del empty params (1×); hyphenate params (8×); |
mNo edit summary |
||
Line 8:
An ''ABI'' defines how data structures or computational routines are accessed in [[machine code]], which is a low-level, hardware-dependent format. In contrast, an [[Application programming interface|''API'']] defines this access in [[source code]], which is a relatively high-level, hardware-independent, often [[human-readable]] format. A common aspect of an ABI is the [[calling convention]], which determines how data is provided as input to, or read as output from, computational routines. Examples of this are the [[x86 calling conventions]].
Adhering to an ABI (which may or may not be officially standardized) is usually the job of a [[compiler]], operating system, or library author. However, an application programmer may have to deal with an ABI directly when writing a program in a mix of programming languages, or even
== Description ==
| |||