FETESTEXCEPT(3POSIX)

💅 fetestexcept — bestie, let's check those floating-point exception flags 💖

okay so real quick before we dive in: this is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (so go peek at the corresponding Linux manual page for the tea on Linux behavior), or honestly the interface may just not be implemented on Linux at all. 🙈

---

✨ PROLOG ✨

This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ — consult the corresponding Linux manual page for details of Linux behavior — or the interface may not be implemented on Linux. either way, girl, check your platform 💅

---

🌸 NAME 🌸

fetestexcept — test floating-point exception flags 🎀

---

🦋 SYNOPSIS 🦋

#include <fenv.h>

int fetestexcept(int excepts);

---

💖 DESCRIPTION 💖

The functionality described on this reference page is aligned with the ISO C standard. Any conflict between the requirements described here and the ISO C standard is unintentional. This volume of POSIX.1‐2017 defers to the ISO C standard. no cap.

So what does fetestexcept() actually do? She determines which of a specified subset of the floating-point exception flags are currently set. The excepts argument specifies the floating-point status flags to be queried. that's it, that's the whole vibe check 🔥

---

👑 RETURN VALUE 👑

fetestexcept() shall return the value of the bitwise-inclusive OR of the floating-point exception macros corresponding to the currently set floating-point exceptions included in excepts. iconic behavior fr fr ✨

---

💀 ERRORS 💀

No errors are defined. literally none. she's unproblematic 😌

The following sections are informative.

---

🌈 EXAMPLES 🌈

The following example calls function f() if an invalid exception is set, and then function g() if an overflow exception is set:

#include <fenv.h>
/* ... */
{
    #pragma STDC FENV_ACCESS ON
    int set_excepts;
    feclearexcept(FE_INVALID | FE_OVERFLOW);
    // maybe raise exceptions
    set_excepts = fetestexcept(FE_INVALID | FE_OVERFLOW);
    if (set_excepts & FE_INVALID) f();
    if (set_excepts & FE_OVERFLOW) g();
    /* ... */
}

look at her go 🫶

---

🧚 APPLICATION USAGE 🧚

None. (yes, really, nothing to add, she said what she said 💅)

---

🍓 RATIONALE 🍓

None. 🎀

---

⭐ FUTURE DIRECTIONS ⭐

None. 🌸

---

💜 SEE ALSO 💜

• feclearexcept()
• fegetexceptflag()
• feraiseexcept()

Also, from the Base Definitions volume of POSIX.1‐2017: <fenv.h> 🦋

---

📜 COPYRIGHT 📜

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group.

In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html . (not me being the messenger tho 😭)

---

and that's the whole page, bestie!! this lil masterpiece came from IEEE/The Open Group, dated 2017, and lives under the name FETESTEXCEPT(3POSIX) — go forth and test those exception flags, you absolute main character 👑💖