Links To ARINC 653 and POSIX
The field covered by ASAAC in Def Stan 00-74 is similar to ARINC 653 (ARINC 653 is a software specification for space and time partitioning in avionics). However, there are differences between the two standards: Some features of ASAAC API, such as file handling, thread managing inside process, or debugging, are not considered in ARINC 653.
However, for the part where the two standards overlap, it is often possible to translate ASAAC interfaces in ARINC 653 API calls (and even in POSIX calls). Approximately 30% of the ASAAC API is covered directly by ARINC 653 and POSIX.
For example, the following call defined in ASAAC:
receiveBufferwould be translated in ARINC 653 by:
RECEIVE_BUFFERand also in POSIX by:
recvRead more about this topic: Allied Standards Avionics Architecture Council
Famous quotes containing the words links to and/or links:
“An alliance is like a chain. It is not made stronger by adding weak links to it. A great power like the United States gains no advantage and it loses prestige by offering, indeed peddling, its alliances to all and sundry. An alliance should be hard diplomatic currency, valuable and hard to get, and not inflationary paper from the mimeograph machine in the State Department.”
—Walter Lippmann (1889–1974)
“An alliance is like a chain. It is not made stronger by adding weak links to it. A great power like the United States gains no advantage and it loses prestige by offering, indeed peddling, its alliances to all and sundry. An alliance should be hard diplomatic currency, valuable and hard to get, and not inflationary paper from the mimeograph machine in the State Department.”
—Walter Lippmann (1889–1974)