FEHOLDEXCEPT(3P)

🌸 FEHOLDEXCEPT(3P) — POSIX Programmer's Manual 🌸

okay bestie, welcome to feholdexcept(3P), straight out of the POSIX Programmer's Manual 💖 this one's short but it's mighty, and it's about saving your floating-point environment before things get chaotic. let's go ✨

---

💫 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.

fr fr, read that twice. Linux might do its own thing, or might not even have this at all. check before you commit 💅

---

👑 NAME

feholdexcept — save current floating-point environment

like, that's the whole vibe. it saves stuff. ✨

---

🎀 SYNOPSIS

#include <fenv.h>

int feholdexcept(fenv_t *envp);

---

🦋 DESCRIPTION

So 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. periodt.

Now the actual tea ☕ — the feholdexcept() function shall:

1. save the current floating-point environment in the object pointed to by envp
2. clear the floating-point status flags
3. and then install a non-stop (continue on floating-point exceptions) mode, if available, for all floating-point exceptions

it's giving "reset the vibe and keep going no matter what" 🌈

---

⭐ RETURN VALUE

The feholdexcept() function shall return zero if and only if non-stop floating-point exception handling was successfully installed.

so zero = slay, nonzero = it didn't work out 💀

---

💜 ERRORS

No errors are defined.

The following sections are informative.

---

🍓 EXAMPLES

None.

(yes bestie, that's the whole section. nothing. nada. she's empty but she's valid 🎀)

---

🧚 APPLICATION USAGE

None.

---

🔥 RATIONALE

The feholdexcept() function should be effective on typical IEC 60559:1989 standard implementations which have the default non-stop mode and at least one other mode for trap handling or aborting. If the implementation provides only the non-stop mode, then installing the non-stop mode is trivial.

lowkey a "congrats on doing nothing" situation when there's only one mode 🙈

---

🌈 FUTURE DIRECTIONS

None.

---

💅 SEE ALSO

• fegetenv()
• feupdateenv()

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 .

---

and that's the whole page, bestie 💖 this icon was brought to you by IEEE/The Open Group, 2017 — mwah, thank you for your service, we love a standards body that ate 🫶✨