Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Remove Nav buttons in footer.

...

Anchor
application binary interface
application binary interface

application binary interface
An interface application binary interface is an interface between two independently compiled modules of a program. An Application Binary Interface document specifies a set of conventions such as the order and location of function arguments that compilers must adhere to in order to achieve interoperability between such modules.

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, and strong exception safety, and no-throw guarantee.)

Anchor
clang
clang

Clangclang
An Clang is an open source C and C++ compiler. More information can be found at http://clang.llvm.org/.

Anchor
condition predicate
condition predicate

condition predicate
An A condition predicate is an expression constructed from the variables of a function that must be true for a thread to be allowed to continue execution.

...

Anchor
criticalsections
criticalsections

critical sections
Code Critical sections are code that accesses shared data , and that would otherwise be protected from data races.

Anchor
cvqualify
cvqualify

cv-qualify
A type that is qualified by either To cv-qualify a type is to add const or volatile (or both) to the type.

Anchor
data race
data race

data race [ISO/IEC 14882-2014]
The execution of a program contains a data race if it contains two potentially concurrent conflicting actions, at least one of which is not atomic, and neither happens before the other, except . [An exception is]that two accesses to the same object of type volatile sig_atomic_t do not result in a data race if both occur in the same thread, even if one or more occurs in a signal handler.

Anchor
deadlock
deadlock

deadlock [ISO/IEC 14882-2014]
A deadlock is when one or more threads are unable to continue execution because each is blocked waiting for one or more of the others to satisfy some condition

Anchor
denial-of-service
denial-of-service

denial-of-service attack
An A denial-of-service attack is an attempt to make a computer resource unavailable to its intended users.

Anchor
diagnostic message
diagnostic message

diagnostic message
 [ISO/IEC 14882-2014]
A diagnostic message is a message belonging to an implementation-defined subset of the implementation’s message output. A diagnostic message may indicate a constraint violation or a valid, but questionable, language construct. Messages typically include the file name and line number pointing to the offending code construct. In addition, implementations also often indicate the severity of the problem. Although the C++ Standard does not specify any such requirement, the most severe problems often cause implementations to fail to fully translate a translation unit. Diagnostics output in such cases are termed errors. Other problems may cause implementations simply to issue a warning message and continue translating the rest of the program. (See error message and warning message.)

Anchor
error
error
 
Anchor
error message
error message

error message

A diagnostic An error message is a diagnostic message generated when source code is encountered that prevents an implementation from translating a translation unit. (See diagnostic message and warning message.)

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,  and strong exception safety, and no-throw guarantee.)

Anchor
exploit
exploit

exploit [Seacord 05a2005]
An exploit is a piece of software or technique that takes advantage of a security vulnerability to violate an explicit or implicit security policy.

Anchor
fatal diagnostic
fatal diagnostic

fatal diagnostic

A fatal diagnostic is a message which causes that causes an implementation not to perform the translation.

Anchor
free store
free store

free store [ISO/IEC 14882-2014]
Storage The free store is 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
gcc
gcc
gcc
GCC
An GCC is an open source C and C++ compiler. More information can be found at https://gcc.gnu.org/.

Anchor
ill-formed
ill-formed
Anchor
ill-formed program
ill-formed program

ill-formed program [ISO/IEC 14882-2014]
A C An ill-formed program is 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:2011]
Particular An implementation is a 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-2014]
BehaviorImplementation-defined behavior is behavior, for a well-formed program construct and correct data, that depends on the implementation and that each implementation documents.

...

Anchor
invalid pointer
invalid pointer

invalid pointer
A An invalid pointer is a pointer that is not a valid pointer.

Anchor
libcxx
libcxx

libc++
An libc++ is an open source Standard Template Library (STL) implementation. More information can be found at http://libcxx.llvm.org/.

Anchor
libstdcxx
libstdcxx

libstdc++
An libstdc++ is an open source Standard Template Library (STL) implementation. More information can be found at https://gcc.gnu.org/onlinedocs/libstdc++/.

Anchor
liveness
liveness

liveness
Every Liveness is when every operation or method invocation executes to completion without interruptions, even if it goes against safety.

...

Anchor
msvc
msvc

Microsoft Visual Studio
A Microsoft Visual Studio is a commercial C and C++ compiler. More information can be found at https://www.visualstudio.com/.

Anchor
msvc stl
msvc stl

Microsoft Visual Studio STL
A commercial The Microsoft Visual Studio STL is a commercial Standard Template Library (STL) implementation. More information can be found at https://msdn.microsoft.com/en-us/library/cscc687y.aspx

Anchor
mitigation
mitigation

mitigation [Seacord 05a2005]
A methodmitigation is a method, technique, process, tool, or runtime library that can prevent or limit exploits against vulnerabilities.

Anchor
one definition rule
one definition rule
Anchor
odr
odr

one-definition rule (ODR) [ISO/IEC 14882-2014]
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, and that every program shall contain exactly one definition of every non-inline function or variable. Some definitions may be duplicated in multiple translation units, subject to strict rules.

Anchor
odr-use
odr-use

ODR-use [ISO/IEC 14882-2014]
A function or object is ODR-used if the address of the entity is taken, the function is called, or a reference is bound to the object. When a function or object is ODR-used, its definition must exist within the program or else the program is ill-formed.

Anchor
RAII
RAII

RAII (Resource Acquisition Is Initialization)
An acronym that stands for: Resource Acquisition Is InitializationRAII is a design principle supported by C++. Holding a resource is a class invariant where the allocation of the resource (acquisition) is inseparable from the initialization of the object during its construction. Further, deallocation of the resource is performed during the destruction of the object. Thus, the resource is held when initialization completes and remains held until finalization begins, ensuring there are no resource leaks unless the object owning the resource is also leaked.

Anchor
reliability
reliability

reliability [IEEE Std 610.12 1990]
The Reliability is the ability of a system or component to perform its required functions under stated conditions for a specified period of time.

Anchor
restricted sink
restricted sink

restricted sink [ISO/IEC 9899:2011]
Operands and arguments A restricted sink is an operand or argument whose domain is a subset of the domain described by their typesits type.

Anchor
rvalue
rvalue

rvalue [ISO/IEC 14882-2014]
An rvalue (so called, historically, because rvalues could appear on the right-hand side of an assignment expression), is an xvalue, a temporary object or subobject thereof, or a value that is not associated with an object.

Anchor
security flaw
security flaw

security flaw [Seacord 05a2005]
A security flaw is a software defect that poses a potential security risk.

Anchor
security policy
security policy

security policy [Internet Society 2000]
A security policy is 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
strong exception safety
strong exception safety

strong exception safety [Stroustrup 01]2001, [ Sutter 002000]
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 and basic exception safety.)

Anchor
SFINAE
SFINAE

SFINAE
SFINAE (Substitution Failure is Is Not An Error)  (SFINAE)
A is a language rule applied by the compiler during overload resolution involving templates. In some contexts, when substituting a template type parameter fails, the specialization is discarded from the overload set instead of causing a compile error. This feature is used in template metaprogramming.

Anchor
tainted source
tainted source

tainted source [ISO/IEC TS 17961:20132012]
External A tainted source is an external source of untrusted data.

NOTE 
Tainted sources include

...

...

Anchor
tainted value
tainted value

tainted value [ISO/IEC TS 17961:20132012]
Value A tainted value is a value derived from a tainted source that has not been sanitized.

Anchor
trust boundary
trust boundary

trust boundary
A trust boundary is a boundary between a trusted execution context (or trusted data source) in which all sub-execution contexts (or data sources) are trusted by the system and a nontrusted execution context (or nontrusted data sink).

Anchor
undefined behavior
undefined behavior

undefined behavior [ISO/IEC 14882-2014]
Behavior Undefined behavior is 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 , or defines the behavior to be ill-formed, with no diagnostic required.

Anchor
unspecified behavior
unspecified behavior

unspecified behavior [ISO/IEC 14882-2014]
Behavior Unspecified behavior is 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:2011]
A valid  An unspecified value is a valid value of the relevant type where the C++ Standard imposes no requirements on which value is chosen in any instance.

Anchor
valid pointer
valid pointer

valid pointer
A valid pointer is 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. 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.

Anchor
vtable
vtable

vtable
A common vtable is a common implementation technique to support dynamic method dispatch, where a class object instance includes a hidden data member that is a pointer to an array of function pointers used to resolve virtual function calls at runtime.

Anchor
vulnerability
vulnerability

vulnerability [Seacord 05a2005]
A vulnerability is a set of conditions that allows an attacker to violate an explicit or implicit security policy.

Anchor
warning
warning
Anchor
warning message
warning message

warning message

A warning message is a diagnostic message generated when source code is encountered that does not prevent an implementation from translating a translation unit. (See diagnostic message and error message.)

Anchor
well-formed
well-formed
Anchor
well-formed program
well-formed program

well-formed program [ISO/IEC 14882-2014]
A Cwell-formed program is a C++ program constructed according to the syntax rules, diagnosable semantic rules, and the one-definition rule. (See also ill-formed program.)

Anchor
xvalue
xvalue

xvalue [ISO/IEC 14882-2014]
An xvalue (an "eXpiring" value) also refers to an object, usually near the end of its lifetime (so that its resources may be moved, for example). An xvalue is the result of certain kinds of expressions involving rvalue references.

 Image Removed Image Removed Image Removed