FEHOLDEXCEPT(3POSIX)

πŸ’– FEHOLDEXCEPT(3POSIX) πŸ’–

okay bestie, so this is a page from the POSIX Programmer's Manual β€” the 3POSIX girlies know. It's the feholdexcept situation and honestly? She's a quiet icon. Let's get into it. ✨


🌸 PROLOG 🌸

This manual page is part of the POSIX Programmer's Manual, no cap.

Heads up fr fr: the Linux implementation of this interface may differ β€” so go check the corresponding Linux manual page for the deets on Linux behavior. Or… the interface might not even be implemented on Linux at all. πŸ’€ So like, vibe check your platform first.

πŸŽ€ NAME πŸŽ€

feholdexcept β€” save current floating-point environment πŸ’Ύ

Like, she's literally the "hold my spot" of floating-point. So real.


✨ SYNOPSIS ✨

#include <fenv.h>

int feholdexcept(fenv_t *envp);

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so the tea: everything described on this reference page is aligned with the ISO C standard. If there's any conflict between what's written here and the ISO C standard? That's unintentional, not a drama. This volume of POSIX.1‐2017 defers to the ISO C standard, periodt.

Now the actual function, bestie:

The feholdexcept() function shall:

  1. save the current floating-point environment into the object pointed to by envp 🫢
  2. clear the floating-point status flags 🧹
  3. then install a non-stop mode β€” that's continue on floating-point exceptions β€” if available, for all floating-point exceptions πŸ”₯

it's giving "snapshot, wipe, and don't freak out at every little exception." iconic behavior honestly.


⭐ RETURN VALUE ⭐

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

if and only if. she said what she said. πŸ‘‘


πŸ’œ ERRORS πŸ’œ

No errors are defined. πŸŽ‰

The following sections are informative β€” meaning they're the lore section, not the rules section. iykyk.


🌈 EXAMPLES 🌈

None. (she's mysterious like that πŸ™ˆ)


πŸ“ APPLICATION USAGE πŸ“

None. (still mysterious πŸ’…)


🧚 RATIONALE 🧚

ok so why does this exist? The feholdexcept() function should be effective on typical IEC 60559:1989 standard implementations β€” the ones that have the default non-stop mode and at least one other mode for trap handling or aborting. slay.

And if the implementation only provides the non-stop mode? Then installing the non-stop mode is… trivial. like, no effort whatsoever. free. πŸ’…


πŸ‘‘ FUTURE DIRECTIONS πŸ‘‘

None. she's stable, she's settled, she's not going anywhere bestie. 🌸


πŸ’– SEE ALSO πŸ’–

  • fegetenv()
  • feupdateenv()
  • The Base Definitions volume of POSIX.1‐2017, <fenv.h>

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 β€” bestie, the original IEEE and The Open Group Standard is the referee document. no arguing with the ref. 🚨

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 absolute baddie of a manual page is brought to you by IEEE/The Open Group, dated 2017, filed under FEHOLDEXCEPT(3POSIX). go save that floating-point environment, you main character. βœ¨πŸ’…πŸŽ€