Anchor |
---|
| abnormal termination |
---|
| abnormal termination |
---|
|
abnormal termination [Open Group 08] Abnormal termination occurs when requested by the
abort()
function or when some signals are received. See also
#normal termination.
Anchor |
---|
| asynchronous-safe |
---|
| asynchronous-safe |
---|
|
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. It must also function properly when global data might itself be in an inconsistent state. Some asynchronous-safe operations are listed Wiki Markup |
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="689bd2cb-b008-4060-ad8b-e925f11dbe24"><ac:parameter ac:name=""> asynchronous-safe</ac:parameter></ac:structured-macro>
*asynchronous-safe* \[[GNU Pth|AA. Bibliography#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. It must also function properly when global data might itself be in an inconsistent state. Some asynchronous-safe operations are listed here:- 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
Few functions are asynchronous-safe. If a function performs any other operations, it is probably not asynchronous-safe.
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="224379da-6cc0-44f0-b09c-8a6578fe99f8"><ac:parameter ac:name=""> availability</ac:parameter></ac:structured-macro>
*availability* \[[IEEE Std 610.12 1990|AA. Bibliography#IEEE Std 610.12 1990]\]
The degree to which a system or component is operational and accessible when required for use. Often expressed as a probability. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="30a42c6a-df86-4a51-a586-81a9a01d170f"><ac:parameter ac:name=""> basic exception safety</ac:parameter></ac:structured-macro>
*basic exception safety* \[[Stroustrup 01|AA. Bibliography#Stroustrup 01]\], \[[Sutter 00|AA. Bibliography#Sutter 00]\]
The basic exception safety guarantee is a property of an operation such that, if the operation terminates by raising an exception, it preserves program state invariants and prevents resource leaks. See also: [exception safety|BB. Definitions#exception safety], [strong exception safety|BB. Definitions#strong exception safety], [no-throw guarantee|BB. Definitions#no-throw guarantee]. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="48176f13-2a10-40f3-a80e-f355d9df583f"><ac:parameter ac:name=""> conforming program</ac:parameter></ac:structured-macro>
*conforming* \[[ISO/IEC 9899-1999|AA. Bibliography#ISO/IEC 9899-1999]\]
Conforming programs may depend upon nonportable features of a conforming implementation. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="26f1814d-85b3-4767-a0a3-db12f4a3a418"><ac:parameter ac:name=""> data race</ac:parameter></ac:structured-macro>
*data race* \[ISO/IEC Document Number N3000 -- Working Draft, Standard for Programming Language C++, November 2009\]
The execution of a program contains a data race if it contains two conflicting actions in different threads, at least one of which is not atomic, and neither happens before the other. Any such data race results in undefined behavior. |
...
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="7315b7bc-24bb-4eb7-9f0a-5c4195798a19"><ac:parameter ac:name=""> error tolerance</ac:parameter></ac:structured-macro>
*error tolerance* \[[IEEE Std 610.12 1990|AA. Bibliography#IEEE Std 610.12 1990]\]
The ability of a system or component to continue normal operation despite the presence of erroneous inputs. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="2996e5bc-78a4-47c7-b944-4f8e6c65feb4"><ac:parameter ac:name=""> exception safety</ac:parameter></ac:structured-macro>
*exception safety* \[[Stroustrup 01|AA. Bibliography#Stroustrup 01]\]
An operation on an object is said to be exception safe if that operation leaves the object in a valid state when the operation is terminated by throwing an exception. See also: [basic exception safety|BB. Definitions#basic exception safety], [strong exception safety|BB. Definitions#strong exception safety], [no-throw guarantee|BB. Definitions#no-throw guarantee]. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="7856d877-fb5b-4122-bb7e-e1e3b64a7ed3"><ac:parameter ac:name=""> exploit</ac:parameter></ac:structured-macro>
*exploit* \[[Seacord 05a|AA. Bibliography#Seacord 05]\]
An exploit is a piece of software or technique that takes advantage of a security vulnerability to violate an explicit or implicit [security policy|BB. Definitions#security policy]. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="a6ce299a-bd70-4ec9-b496-d30ce83c8def"><ac:parameter ac:name=""> fail safe</ac:parameter></ac:structured-macro>
*fail safe* \[[IEEE Std 610.12 1990|AA. Bibliography#IEEE Std 610.12 1990]\]
Pertaining to a system or component that automatically places itself in a safe operating mode in the event of a failure; for example, a traffic light that reverts to blinking red in all directions when normal operation fails. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="547f90e3-9b28-46a3-986a-6ec242ff031d"><ac:parameter ac:name=""> fail soft</ac:parameter></ac:structured-macro>
*fail soft* \[[IEEE Std 610.12 1990|AA. Bibliography#IEEE Std 610.12 1990]\]
Pertaining to a system or component that continues to provide partial operational capability in the event of certain failures; for example, a traffic light that continues to alternate between red and green if the yellow light fails. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="e6509f28-64c5-4a42-8a9c-8143e0256368"><ac:parameter ac:name=""> fault tolerance</ac:parameter></ac:structured-macro>
*fault tolerance* \[[IEEE Std 610.12 1990|AA. Bibliography#IEEE Std 610.12 1990]\]
The ability of a system or component to continue normal operation despite the presence of hardware or software faults. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="f3974ad6-ad1e-4caa-9d16-7588eec303b3"><ac:parameter ac:name=""> free store</ac:parameter></ac:structured-macro>
*free store* \[[ISO/IEC 14882-2003| AA. Bibliography#ISO/IEC 14882-2003]\]
Storage managed by the C++ allocation and deallocation functions {{::operator new(std::size_t)}}, {{::operator delete(void*)}}, their array forms {{::operator new[](std::size_t)}}, {{::operator delete[](void*)}}, overloads of said functions on {{std::nothrow_t}}, any user-defined replacements for said functions, as well as any such functions defined as a member of a class. Storage in the free store is distinct from storage managed by the C functions {{calloc}}, {{free}}, {{malloc}}, and {{realloc}}. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="a26d71b5-d657-4289-8fe6-e2aa2aef25c1"><ac:parameter ac:name=""> freestanding environment</ac:parameter></ac:structured-macro> <ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="c88ff59c-f63c-4abe-932c-53b151c6bf2e"><ac:parameter ac:name=""> freestanding implementation</ac:parameter></ac:structured-macro>
*freestanding implementation* \[[ISO/IEC 14882-2003| AA. Bibliography#ISO/IEC 14882-2003]\]
A freestanding implementation is one in which execution may take place without the benefit of an operating system, and has an implementation-defined set of libraries that includes certain language-support libraries. Also referred to as _freestanding environment_. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="489849f6-b217-4343-985b-da63375bee83"><ac:parameter ac:name=""> function-like macro</ac:parameter></ac:structured-macro>
*function-like macro* \[[ISO/IEC 9899-1999|AA. Bibliography#ISO/IEC 9899-1999]\]
A {{#define}} preprocessing directive that defines an identifier immediately followed by zero or more parameters, the ellipsis ({{...}}), or a combination of the two, enclosed in parentheses, similar syntactically to a function call. Subsequent instances of the macro name followed by a parenthesized list of arguments in a translation unit are replaced by the replacement list of preprocessing tokens that constitute the remainder of the directive. See also [#object-like macro] and [#unsafe function-like macro]. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="26b29f62-da93-4790-ab32-51c06f1efa96"><ac:parameter ac:name=""> hosted environment</ac:parameter></ac:structured-macro> <ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="82dd9e68-2c74-4358-b9ac-ee69949b934a"><ac:parameter ac:name=""> hosted implementation</ac:parameter></ac:structured-macro>
*hosted implementation* \[[ISO/IEC 14882-2003| AA. Bibliography#ISO/IEC 14882-2003]\]
An implementation that is not freestanding. Program startup occurs at {{main()}}, complex types are implemented, and all C++ standard library facilities are available. Also referred to as _hosted environment_. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="28790eaa-8064-4797-b1ed-5414207f6231"><ac:parameter ac:name="">ill-formed</ac:parameter></ac:structured-macro> <ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="e98b9b63-acc3-41a1-84f3-d5a2589edec6"><ac:parameter ac:name="">ill-formed program</ac:parameter></ac:structured-macro>
*ill-formed program* \[[ISO/IEC 14882-2003| AA. Bibliography#ISO/IEC 14882-2003]\]
A C++ program that is not [#well-formed], that is a program not constructed according to the syntax rules, diagnosable semantic rules, and the [#One Definition Rule]. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="b392277c-8837-4676-aed4-7e1982ea2209"><ac:parameter ac:name=""> implementation</ac:parameter></ac:structured-macro>
*implementation* \[[ISO/IEC 9899-1999|AA. Bibliography#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. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="79997d57-c696-4298-bfc1-2dc73d55228e"><ac:parameter ac:name=""> implementation-defined behavior</ac:parameter></ac:structured-macro>
*implementation-defined behavior* \[[ISO/IEC 14882-2003|AA. Bibliography#ISO/IEC 14882-2003]\]
Behavior, for a [#well-formed program] construct and correct data, that depends on the implementation and that each implementation shall document. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="d85d6156-edf6-4922-81fa-304989699317"><ac:parameter ac:name=""> incomplete type</ac:parameter></ac:structured-macro>
*incomplete type* \[[ISO/IEC 14882-2003| AA. Bibliography#ISO/IEC 14882-2003]\]
A type that describes objects but lacks information needed to determine their sizes. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="0968e66d-dde1-45f6-944e-eb572f420048"><ac:parameter ac:name=""> indeterminate value</ac:parameter></ac:structured-macro>
*indeterminate value* \[[ISO/IEC 9899-1999|AA. Bibliography#ISO/IEC 9899-1999]\]
Either an [#unspecified value] or a [#trap representation]. |
...
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="f7af1892-5f45-478e-bff2-4bbb313c0272"><ac:parameter ac:name=""> locale-specific behavior</ac:parameter></ac:structured-macro>
*locale-specific behavior* \[[ISO/IEC 14882-2003| AA. Bibliography#ISO/IEC 14882-2003]\]
Behavior that depends on local conventions of nationality, culture, and language that each implementation documents. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="f8607411-44ae-4484-9a91-4e1d0368a9af"><ac:parameter ac:name=""> lvalue</ac:parameter></ac:structured-macro>
*lvalue* \[[ISO/IEC 9899-1999|AA. Bibliography#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". |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="dfab8326-92e9-4613-af4f-a046a0005838"><ac:parameter ac:name=""> mitigation</ac:parameter></ac:structured-macro>
*mitigation* \[[Seacord 05a|AA. Bibliography#Seacord 05]\]
Mitigations are methods, techniques, processes, tools, or runtime libraries that can prevent or limit exploits against vulnerabilities. |
...
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="1470b367-e19e-4526-b793-ff93992e8cab"><ac:parameter ac:name=""> no-throw guarantee</ac:parameter></ac:structured-macro>
*no-throw guarantee* \[[Sutter 00|AA. Bibliography#Sutter 00]\]
The no-throw guarantee is a property of an operation such that it is guaranteed to complete successfully without raising or propagating an exception. See also: [exception safety|BB. Definitions#exception safety], [basic exception safety|BB. Definitions#basic exception safety], [strong exception safety|BB. Definitions#strong exception safety]. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="1458d535-3aad-4604-9cce-0eeed3ce4723"><ac:parameter ac:name=""> object-like macro</ac:parameter></ac:structured-macro>
*object-like macro* \[[ISO/IEC 9899-1999|AA. Bibliography#ISO/IEC 9899-1999]\]
A {{#define}} preprocessing directive that defines an identifier with no parentheses. Subsequent instances of the macro name in a translation unit are replaced by the replacement list of preprocessing tokens that constitute the remainder of the directive. See also [#function-like macro]. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="0a25655c-5fef-4759-af71-909453731764"><ac:parameter ac:name="">one definition rule</ac:parameter></ac:structured-macro> <ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="7b05eb7b-9b3e-4456-b63a-ebd74dc50ed5"><ac:parameter ac:name="">odr</ac:parameter></ac:structured-macro>
*one definition rule (ODR)* \[[ISO/IEC 14882-2003| AA. Bibliography#ISO/IEC 14882-2003]\]
A fundamental C++ rule that states that no translation unit shall contain more than one definition of any variable, function, class type, enumeration type or template. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="e9f8f177-10e7-4f2e-a059-cfbbdd1c2cb6"><ac:parameter ac:name=""> reentrant</ac:parameter></ac:structured-macro>
*reentrant* \[[Dowd 06|AA. Bibliography#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. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="38a60db0-5c2b-45d6-90d2-4a60bdbea412"><ac:parameter ac:name=""> reliability</ac:parameter></ac:structured-macro>
*reliability* \[[IEEE Std 610.12 1990|AA. Bibliography#IEEE Std 610.12 1990]\]
The ability of a system or component to perform its required functions under stated conditions for a specified period of time. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="4fa37252-e172-4ebb-ad86-c247e03b0121"><ac:parameter ac:name=""> robustness</ac:parameter></ac:structured-macro>
*robustness* \[[IEEE Std 610.12 1990|AA. Bibliography#IEEE Std 610.12 1990]\]
The degree to which a system or component can function correctly in the presence of invalid inputs or stressful environmental conditions. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="a6653a5b-05a7-4452-aeae-422ffb278b5e"><ac:parameter ac:name=""> rvalue</ac:parameter></ac:structured-macro>
*rvalue* \[[ISO/IEC 9899-1999|AA. Bibliography#ISO/IEC 9899-1999]\]
Value of an expression. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="5792e4a2-db69-41e0-8888-11aa14cf9446"><ac:parameter ac:name=""> security flaw</ac:parameter></ac:structured-macro>
*security flaw* \[[Seacord 05a|AA. Bibliography#Seacord 05]\]
A security flaw is a software defect that poses a potential security risk. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="334dd8cf-a2a6-4429-8e06-8ffab72b87af"><ac:parameter ac:name=""> security policy</ac:parameter></ac:structured-macro>
*security policy* \[[Internet Society 00|AA. Bibliography#Internet Society 00]\]
A set of rules and practices that specify or regulate how a system or organization provides security services to protect sensitive and critical system resources. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="d3bbb59b-e12d-425c-8087-59094347d351"><ac:parameter ac:name=""> sequence point</ac:parameter></ac:structured-macro>
*sequence point* C99 \[[ISO/IEC 9899-1999|AA. Bibliography#ISO/IEC 9899-1999]\]
Evaluation of an expression may produce side effects. At specific points in the execution sequence called _sequence points_, all side effects of previous evaluations have completed, and no side effects of subsequent evaluations have yet taken place. |
Wiki Markup |
---|
The following sequence points are defined by C99 \[[ISO/IEC 9899-1999|AA. Bibliography#ISO/IEC 9899-1999]\]: |
- the call to a function, after the arguments have been evaluated
- the end of the first operand of the following operators: && (logical AND); || (logical OR); ? (conditional); , (comma operator)
- the end of a full declarator
- the end of a full expression: an initializer; the expression in an expression statement (that is, at the semicolon); the controlling expression of a selection statement (if or switch); the controlling expression of a while or do statement; each of the expressions of a for statement; the expression in a return statement
- immediately before a function returns
- after the actions associated with each formatted input/output function conversion specifier
- immediately before and immediately after each call to a comparison function, by a standard searching or sorting function, and between any call to a comparison function and any movement of the objects passed as arguments to that call
Note that not all instances of a comma in C code denote a usage of the comma operator. For example, the comma between arguments in a function call is not a sequence point.
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="89d6c593-9754-44a1-a766-858d2f78e3f1"><ac:parameter ac:name=""> strictly conforming</ac:parameter></ac:structured-macro>
*strictly conforming* \[[ISO/IEC 9899-1999|AA. Bibliography#ISO/IEC 9899-1999]\]
A strictly conforming program is one that uses only those features of the language and library specified in the international standard. Strictly conforming programs are intended to be maximally portable among conforming implementations and can't, for example, depend upon implementation-defined behavior. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="9703dacf-5fe7-404b-b6e5-59f95e0eb274"><ac:parameter ac:name=""> strong exception safety</ac:parameter></ac:structured-macro>
*strong exception safety* \[[Stroustrup 01|AA. Bibliography#Stroustrup 01]\], \[[Sutter 00|AA. Bibliography#Sutter 00]\]
The strong exception safety guarantee is a property of an operation such that, in addition to satisfying the [basic exception safety|BB. Definitions#basic exception safety] guarantee, if the operation terminates by raising an exception it has no observable effects on program state. See also: [exception safety|BB. Definitions#exception safety], [basic exception safety|BB. Definitions#basic exception safety], [no-throw guarantee|BB. Definitions#no-throw guarantee]. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="a371e4ac-00ac-4d20-adc5-4f926e619928"><ac:parameter ac:name="">trap representation</ac:parameter></ac:structured-macro>
*trap representation* \[[ISO/IEC 9899-1999|AA. Bibliography#ISO/IEC 9899-1999]\]
Object representation that does not represent a value of the object type. Attempting to read the value of an object that has a trap representation other than by an expression that has a character type is [undefined | #undefined behavior]. Producing such a representation by a side effect that modifies all or any part of the object other than by an expression that has a character type is undefined. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="3bfd4cd7-31d7-41b7-be20-24ca7e3f6885"><ac:parameter ac:name=""> undefined behavior</ac:parameter></ac:structured-macro>
*undefined behavior* \[[ISO/IEC 14882-2003| AA. Bibliography#ISO/IEC 14882-2003]\]
Behavior, such as might arise upon use of an erroneous program construct or erroneous data, for which the C++ Standard imposes no requirements. Undefined behavior may also be expected when the C++ Standard omits the description of any explicit definition of behavior. |
...
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="b6e3908a-fadf-417f-a1d3-8ff19dca0513"><ac:parameter ac:name=""> unspecified behavior</ac:parameter></ac:structured-macro>
*unspecified behavior* \[[ISO/IEC 14882-2003| AA. Bibliography#ISO/IEC 14882-2003]\]
Behavior, for a [#well-formed program] construct and correct data, that depends on the implementation. The implementation is not required to document which behavior occurs. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="c1491e87-c471-4632-8deb-2823bf7b85d7"><ac:parameter ac:name=""> unspecified value</ac:parameter></ac:structured-macro>
*unspecified value* \[[ISO/IEC 9899-1999|AA. Bibliography#ISO/IEC 9899-1999]\]
A valid value of the relevant type where the C++ Standard imposes no requirements on which value is chosen in any instance. An unspecified value cannot be a [#trap representation]. |
...
Anchor |
---|
| availability |
---|
| availability |
---|
|
availability [IEEE Std 610.12 1990] The degree to which a system or component is operational and accessible when required for use. Often expressed as a probability. Anchor |
---|
| basic exception safety |
---|
| basic exception safety |
---|
|
basic exception safety [Stroustrup 01], [Sutter 00] The basic exception safety guarantee is a property of an operation such that, if the operation terminates by raising an exception, it preserves program state invariants and prevents resource leaks. See also: exception safety, strong exception safety, no-throw guarantee. Anchor |
---|
| conforming program |
---|
| conforming program |
---|
|
conforming [ISO/IEC 9899-1999] Conforming programs may depend upon nonportable features of a conforming implementation. data race [ISO/IEC Document Number N3000 – Working Draft, Standard for Programming Language C++, November 2009] The execution of a program contains a data race if it contains two conflicting actions in different threads, at least one of which is not atomic, and neither happens before the other. Any such data race results in undefined behavior. deadlock A condition where one or more threads is unable to continue execution because it is blocked waiting for some thread (including itself) to satisfy some condition. Anchor |
---|
| denial-of-service |
---|
| denial-of-service |
---|
|
denial-of-service attack An attempt to make a computer resource unavailable to its intended users. Anchor |
---|
| error tolerance |
---|
| error tolerance |
---|
|
error tolerance [IEEE Std 610.12 1990] The ability of a system or component to continue normal operation despite the presence of erroneous inputs. Anchor |
---|
| exception safety |
---|
| exception safety |
---|
|
exception safety [Stroustrup 01] An operation on an object is said to be exception safe if that operation leaves the object in a valid state when the operation is terminated by throwing an exception. See also: basic exception safety, strong exception safety, no-throw guarantee. exploit [Seacord 05a] An exploit is a piece of software or technique that takes advantage of a security vulnerability to violate an explicit or implicit security policy. fail safe [IEEE Std 610.12 1990] Pertaining to a system or component that automatically places itself in a safe operating mode in the event of a failure; for example, a traffic light that reverts to blinking red in all directions when normal operation fails. fail soft [IEEE Std 610.12 1990] Pertaining to a system or component that continues to provide partial operational capability in the event of certain failures; for example, a traffic light that continues to alternate between red and green if the yellow light fails. Anchor |
---|
| fault tolerance |
---|
| fault tolerance |
---|
|
fault tolerance [IEEE Std 610.12 1990] The ability of a system or component to continue normal operation despite the presence of hardware or software faults. free store [ISO/IEC 14882-2003] Storage managed by the C++ allocation and deallocation functions ::operator new(std::size_t)
, ::operator delete(void*)
, their array forms ::operator new[](std::size_t)
, ::operator delete[](void*)
, overloads of said functions on std::nothrow_t
, any user-defined replacements for said functions, as well as any such functions defined as a member of a class. Storage in the free store is distinct from storage managed by the C functions calloc
, free
, malloc
, and realloc
. Anchor |
---|
| freestanding environment |
---|
| freestanding environment |
---|
|
Anchor |
---|
| freestanding implementation |
---|
| freestanding implementation |
---|
|
freestanding implementation [ISO/IEC 14882-2003] A freestanding implementation is one in which execution may take place without the benefit of an operating system, and has an implementation-defined set of libraries that includes certain language-support libraries. Also referred to as freestanding environment. Anchor |
---|
| function-like macro |
---|
| function-like macro |
---|
|
function-like macro [ISO/IEC 9899-1999] A #define
preprocessing directive that defines an identifier immediately followed by zero or more parameters, the ellipsis (...
), or a combination of the two, enclosed in parentheses, similar syntactically to a function call. Subsequent instances of the macro name followed by a parenthesized list of arguments in a translation unit are replaced by the replacement list of preprocessing tokens that constitute the remainder of the directive. See also #object-like macro and #unsafe function-like macro. Anchor |
---|
| hosted environment |
---|
| hosted environment |
---|
|
Anchor |
---|
| hosted implementation |
---|
| hosted implementation |
---|
|
hosted implementation [ISO/IEC 14882-2003] An implementation that is not freestanding. Program startup occurs at main()
, complex types are implemented, and all C++ standard library facilities are available. Also referred to as hosted environment. Anchor |
---|
| ill-formed program |
---|
| ill-formed program |
---|
|
ill-formed program [ISO/IEC 14882-2003] A C++ program that is not #well-formed, that is a program not constructed according to the syntax rules, diagnosable semantic rules, and the #One Definition Rule. Anchor |
---|
| implementation |
---|
| implementation |
---|
|
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. Anchor |
---|
| implementation-defined behavior |
---|
| implementation-defined behavior |
---|
|
implementation-defined behavior [ISO/IEC 14882-2003] Behavior, for a #well-formed program construct and correct data, that depends on the implementation and that each implementation shall document. Anchor |
---|
| incomplete type |
---|
| incomplete type |
---|
|
incomplete type [ISO/IEC 14882-2003] A type that describes objects but lacks information needed to determine their sizes. Anchor |
---|
| indeterminate value |
---|
| indeterminate value |
---|
|
indeterminate value [ISO/IEC 9899-1999] Either an #unspecified value or a #trap representation. Anchor |
---|
| invalid pointer |
---|
| invalid pointer |
---|
|
invalid pointer A pointer that is not a #valid pointer. Anchor |
---|
| locale-specific behavior |
---|
| locale-specific behavior |
---|
|
locale-specific behavior [ISO/IEC 14882-2003] Behavior that depends on local conventions of nationality, culture, and language that each implementation documents. 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". mitigation [Seacord 05a] Mitigations are methods, techniques, processes, tools, or runtime libraries that can prevent or limit exploits against vulnerabilities. Anchor |
---|
| normal termination |
---|
| normal termination |
---|
|
normal termination [Open Group 08] Normal termination occurs by a return from main()
, when requested with the exit()
, _exit()
, or _Exit()
functions; or when the last thread in the process terminates by returning from its start function, by calling the pthread_exit()
function, or through cancellation. See also #abnormal termination. Anchor |
---|
| no-throw guarantee |
---|
| no-throw guarantee |
---|
|
no-throw guarantee [Sutter 00] The no-throw guarantee is a property of an operation such that it is guaranteed to complete successfully without raising or propagating an exception. See also: exception safety, basic exception safety, strong exception safety. Anchor |
---|
| object-like macro |
---|
| object-like macro |
---|
|
object-like macro [ISO/IEC 9899-1999] A #define
preprocessing directive that defines an identifier with no parentheses. Subsequent instances of the macro name in a translation unit are replaced by the replacement list of preprocessing tokens that constitute the remainder of the directive. See also #function-like macro. Anchor |
---|
| one definition rule |
---|
| one definition rule |
---|
|
one definition rule (ODR) [ISO/IEC 14882-2003] A fundamental C++ rule that states that no translation unit shall contain more than one definition of any variable, function, class type, enumeration type or template. 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. reliability [IEEE Std 610.12 1990] The ability of a system or component to perform its required functions under stated conditions for a specified period of time. robustness [IEEE Std 610.12 1990] The degree to which a system or component can function correctly in the presence of invalid inputs or stressful environmental conditions. rvalue [ISO/IEC 9899-1999] Value of an expression. Anchor |
---|
| security flaw |
---|
| security flaw |
---|
|
security flaw [Seacord 05a] A security flaw is a software defect that poses a potential security risk. Anchor |
---|
| security policy |
---|
| security policy |
---|
|
security policy [Internet Society 00] A set of rules and practices that specify or regulate how a system or organization provides security services to protect sensitive and critical system resources. Anchor |
---|
| sequence point |
---|
| sequence point |
---|
|
sequence point C99 [ISO/IEC 9899-1999] Evaluation of an expression may produce side effects. At specific points in the execution sequence called sequence points, all side effects of previous evaluations have completed, and no side effects of subsequent evaluations have yet taken place.The following sequence points are defined by C99 [ISO/IEC 9899-1999]:
- the call to a function, after the arguments have been evaluated
- the end of the first operand of the following operators: && (logical AND); || (logical OR); ? (conditional); , (comma operator)
- the end of a full declarator
- the end of a full expression: an initializer; the expression in an expression statement (that is, at the semicolon); the controlling expression of a selection statement (if or switch); the controlling expression of a while or do statement; each of the expressions of a for statement; the expression in a return statement
- immediately before a function returns
- after the actions associated with each formatted input/output function conversion specifier
- immediately before and immediately after each call to a comparison function, by a standard searching or sorting function, and between any call to a comparison function and any movement of the objects passed as arguments to that call
Note that not all instances of a comma in C code denote a usage of the comma operator. For example, the comma between arguments in a function call is not a sequence point.
Anchor |
---|
| strictly conforming |
---|
| strictly conforming |
---|
|
strictly conforming [ISO/IEC 9899-1999] A strictly conforming program is one that uses only those features of the language and library specified in the international standard. Strictly conforming programs are intended to be maximally portable among conforming implementations and can't, for example, depend upon implementation-defined behavior. Anchor |
---|
| strong exception safety |
---|
| strong exception safety |
---|
|
strong exception safety [Stroustrup 01], [Sutter 00] The strong exception safety guarantee is a property of an operation such that, in addition to satisfying the basic exception safety guarantee, if the operation terminates by raising an exception it has no observable effects on program state. See also: exception safety, basic exception safety, no-throw guarantee. Anchor |
---|
| trap representation |
---|
| trap representation |
---|
|
trap representation [ISO/IEC 9899-1999] Object representation that does not represent a value of the object type. Attempting to read the value of an object that has a trap representation other than by an expression that has a character type is undefined . Producing such a representation by a side effect that modifies all or any part of the object other than by an expression that has a character type is undefined. Anchor |
---|
| undefined behavior |
---|
| undefined behavior |
---|
|
undefined behavior [ISO/IEC 14882-2003] Behavior, such as might arise upon use of an erroneous program construct or erroneous data, for which the C++ Standard imposes no requirements. Undefined behavior may also be expected when the C++ Standard omits the description of any explicit definition of behavior. Anchor |
---|
| unsafe function-like macro |
---|
| unsafe function-like macro |
---|
|
unsafe function-like macro A #function-like macro whose expansion causes one or more of its arguments not to be evaluated exactly once. Anchor |
---|
| unspecified behavior |
---|
| unspecified behavior |
---|
|
unspecified behavior [ISO/IEC 14882-2003] Behavior, for a #well-formed program construct and correct data, that depends on the implementation. The implementation is not required to document which behavior occurs. Anchor |
---|
| unspecified value |
---|
| unspecified value |
---|
|
unspecified value [ISO/IEC 9899-1999] A valid value of the relevant type where the C++ Standard imposes no requirements on which value is chosen in any instance. An unspecified value cannot be a #trap representation. Anchor |
---|
| valid pointer |
---|
| valid pointer |
---|
|
valid pointer A pointer that refers to an element within an array or one past the last element of an array. For the purposes of this definition, a pointer to an object that is not an element of an array behaves the same as a pointer to the first element of an array of length one with the type of the object as its element type. (Cf 6.5.8p3) For the purposes of this definition, an object can be considered to be an array of a certain number of bytes; that number is the size of the object, as produced by the sizeof
operator. validation [IEC 61508-4] Confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use are fulfilled. Anchor |
---|
| verification |
---|
| verification |
---|
|
verification [IEC 61508-4] Confirmation by examination and provision of objective evidence that the requirements have been fulfilled. Anchor |
---|
| vulnerability |
---|
| vulnerability |
---|
|
vulnerability [Seacord 05a] A vulnerability is a set of conditions that allows an attacker to violate an explicit or implicit security policy. Anchor |
---|
| well-formed program |
---|
| well-formed program |
---|
|
well-formed program [ISO/IEC 14882-2003] A C++ program constructed according to the syntax rules, diagnosable semantic rules, and the #One Definition Rule. See also #ill-formed program Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="981f0706-b434-439d-9412-26cd183b38e8"><ac:parameter ac:name=""> validation</ac:parameter></ac:structured-macro>
*validation* \[[IEC 61508-4|AA. Bibliography#IEC 61508-4]\]
Confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use are fulfilled. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="7442075f-6746-49f0-b7a9-6ddc475e8bcd"><ac:parameter ac:name=""> verification</ac:parameter></ac:structured-macro>
*verification* \[[IEC 61508-4|AA. Bibliography#IEC 61508-4]\]
Confirmation by examination and provision of objective evidence that the requirements have been fulfilled. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="9e80d1de-feb5-466d-a917-4fdb1b8a2158"><ac:parameter ac:name=""> vulnerability</ac:parameter></ac:structured-macro>
*vulnerability* \[[Seacord 05a|AA. Bibliography#Seacord 05]\]
A vulnerability is a set of conditions that allows an attacker to violate an explicit or implicit security policy. |
Wiki Markup |
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="035a6405-9a2d-4975-887b-8f232690bdf8"><ac:parameter ac:name="">well-formed</ac:parameter></ac:structured-macro> <ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="5eaa7fa4-14ee-4172-9cda-0ac359834c83"><ac:parameter ac:name="">well-formed program</ac:parameter></ac:structured-macro>
*well-formed program* \[[ISO/IEC 14882-2003| AA. Bibliography#ISO/IEC 14882-2003]\]
A C++ program constructed according to the syntax rules, diagnosable semantic rules, and the [#One Definition Rule]. See also [#ill-formed program].