BB. Definitions

<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="717b80aa-7aad-4695-a46c-d1d366226eba"><ac:parameter ac:name=""> asynchronous-safe</ac:parameter></ac:structured-macro>
asynchronous-safe [[GNU Pth]]
A function is asynchronous-safe, or asynchronous-signal safe, if it can be called safely and without side effects from within a signal handler context. That is, it must be able to be interrupted at any point and run linearly out of sequence without causing an inconsistent state. Some asynchronous-safe operations are listed below:

• call the signal() function to reinstall a signal handler
• unconditionally modify a volatile sig_atomic_t variable (as modification to this type is atomic)
• call the _Exit() function to immediately terminate program execution
• invoke an asynchronous-safe function, as specified by your implementation

Very few functions are asynchronous-safe. If a function performs any other operations, it is probably not asynchronous-safe.

{anchor: freestanding environment}
freestanding environment [[ISO/IEC 9899-1999]]
An environment in which C program execution may take place without any benefit of an operating system.  Program startup might occur at some function other than main(), complex types might not be implemented, and only certain minimal library facilities are guaranteed to be available.

{anchor: hosted environment}
hosted environment [[ISO/IEC 9899-1999]]
An environment that is not freestanding.  Program startup occurs at main(), complex types are implemented, and all C standard library facilities are available.

<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="366998ba-f23d-431e-b544-a2c0e663dae3"><ac:parameter ac:name=""> implementation</ac:parameter></ac:structured-macro>
implementation [[ISO/IEC 9899-1999]]
Particular set of software, running in a particular translation environment under particular control options, that performs translation of programs for, and supports execution of functions in, a particular execution environment.

<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="e4137b05-0b87-422f-aa86-89ed4b3027b6"><ac:parameter ac:name=""> implementation-defined behavior</ac:parameter></ac:structured-macro>
implementation-defined behavior [[ISO/IEC 9899-1999]]
Unspecified behavior where each implementation documents how the choice is made.

<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="e5cb5b83-8d5f-4dd1-80f2-66940cc4d897"><ac:parameter ac:name=""> locale-specific behavior</ac:parameter></ac:structured-macro>
locale-specific behavior [[ISO/IEC 9899-1999]]
Behavior that depends on local conventions of nationality, culture, and language that each implementation documents.

<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="4d8a5338-14d2-4d3b-86df-e26cb2186b94"><ac:parameter ac:name=""> lvalue</ac:parameter></ac:structured-macro>
lvalue [[ISO/IEC 9899-1999]]
An lvalue is an expression with an object type or an incomplete type other than void. The name "lvalue" comes originally from the assignment expression E1 = E2, in which the left operand E1 is required to be a (modifiable) lvalue. It is perhaps better considered as representing an object "locator value".

<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="23f9c67b-dca7-40eb-94dd-3549bdc1f306"><ac:parameter ac:name=""> reentrant</ac:parameter></ac:structured-macro>
reentrant [[Dowd 06]]
A function is reentrant if multiple instances of the same function can run in the same address space concurrently without creating the potential for inconsistent states.

<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="6c8b3bba-bfb3-4a43-a58e-cf04af71acaf"><ac:parameter ac:name=""> rvalue</ac:parameter></ac:structured-macro>
rvalue [[ISO/IEC 9899-1999]]
Value of an expression.

<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="df629ef5-acaf-444c-8b51-333a851063b1"><ac:parameter ac:name=""> undefined behavior</ac:parameter></ac:structured-macro>
undefined behavior [[ISO/IEC 9899-1999]]
Behavior, upon use of a nonportable or erroneous program construct or of erroneous data, for which the standard imposes no requirements. An example of undefined behavior is the behavior on integer overflow.

<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="41ac49e9-2f0c-46e9-a5ba-cfbf77cff0b6"><ac:parameter ac:name=""> unspecified behavior</ac:parameter></ac:structured-macro>
unspecified behavior [[ISO/IEC 9899-1999]]
Behavior where the standard provides two or more possibilities and imposes no further requirements on which is chosen in any instance.

<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="3b559a5b-f98d-408a-90d8-b7ad6e1159bc"><ac:parameter ac:name=""> validation</ac:parameter></ac:structured-macro>
validation [[IEC 61508-4]]
Confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use are fulfilled.

<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="01b89ec6-726c-427b-b49d-aafe8894cc4d"><ac:parameter ac:name=""> verification</ac:parameter></ac:structured-macro>
verification [[IEC 61508-4]]
Confirmation by examination and provision of objective evidence that the requirements have been fulfilled.