Lines Matching full:functions

6 Finds specific constructs in signal handler functions that can cause undefined
11 - Calls to non-asynchronous-safe functions are not allowed.
15 - Calls to non-asynchronous-safe functions are not allowed.
18 - Calls to functions with non-C linkage are not allowed (including the signal
24 of known functions. In addition, the function must come from a system header
28 including user functions for which only the declaration is visible.
29 Calls to user-defined functions with visible definitions are checked
33 `SIG30-C. Call only asynchronous-safe functions within signal handlers
34 …ding.cert.org/confluence/display/c/SIG30-C.+Call+only+asynchronous-safe+functions+within+signal+ha…
45   Selects which set of functions is considered as asynchronous-safe
50      and includes functions ``abort()``, ``_Exit()``, ``quick_exit()`` and
53      Selects a larger set of functions that is listed in POSIX.1-2017 (see `this
55      <https://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_04_03>`_
56      for more information). The following functions are included:
95      is included here in the set of safe functions.