...
| Anchor |
|---|
| async-signal-safe |
|---|
| async-signal-safe |
|---|
|
async-signal-safe function [
ISO/IEC 9945:2008]
A function that may be invoked, without restriction, from signal-catching functions. No function (defined in ISO/IEC 9945) is async-signal-safe unless explicitly described as such. See
asynchronous-safe.
| Anchor |
|---|
| asynchronous-safe |
|---|
| asynchronous-safe |
|---|
|
| Anchor |
|---|
| asynchronous-safe function |
|---|
| asynchronous-safe function |
|---|
|
| Anchor |
|---|
| async-signal-safe |
|---|
| async-signal-safe |
|---|
|
asynchronous-safe function [
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 to 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:
...
| Anchor |
|---|
| function-like macro |
|---|
| function-like macro |
|---|
|
function-like macro [
ISO/IEC 9899:2011]
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
object-like macro and
unsafe function-like macro.
| Anchor |
|---|
| hosted environment |
|---|
| hosted environment |
|---|
|
hosted environment [
ISO/IEC 9899:2011]
An environment that is not freestanding. Program startup occurs at
main(), complex types are implemented, and all C standard library facilities are available.
...
