LLROUND(3P)

πŸ’– LLROUND β€” POSIX Programmer's Manual, section 3P πŸ’–

okay bestie, so this is a page from the POSIX Programmer's Manual, and it's giving llround(3P) energy. ✨

🫢 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 at all. 😭 so like, check first, fr fr.


🌸 NAME 🌸

llround, llroundf, llroundl β€” round to nearest integer value


✨ SYNOPSIS ✨

#include <math.h>

long long llround(double x);
long long llroundf(float x);
long long llroundl(long double x);

three lil besties, one job πŸ’…


πŸ’œ 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. periodt.

These functions shall round their argument to the nearest integer value, rounding halfway cases away from zero, regardless of the current rounding direction. so like, 2.5 goes up, -2.5 goes down-down, and nothing about your current rounding mode changes that. iconic behavior honestly. πŸ’…

An application wishing to check for error situations should set errno to zero and call feclearexcept(FE_ALL_EXCEPT) before calling these functions. On return, if errno is non-zero or fetestexcept(FE_INVALID | FE_DIVBYZERO | FE_OVERFLOW | FE_UNDERFLOW) is non-zero, an error has occurred. πŸ‘€ that's your vibe check, do it before and after.


πŸŽ€ RETURN VALUE πŸŽ€

Upon successful completion, these functions shall return the rounded integer value. slay. πŸ₯³

  • If x is NaN, a domain error shall occur, and an unspecified value is returned.
  • If x is +Inf, a domain error shall occur and an unspecified value is returned.
  • If x is -Inf, a domain error shall occur and an unspecified value is returned.
  • If the correct value is positive and too large to represent as a long long, an unspecified value shall be returned. On systems that support the IEC 60559 Floating-Point option, a domain error shall occur; otherwise, a domain error may occur.
  • If the correct value is negative and too large to represent as a long long, an unspecified value shall be returned. On systems that support the IEC 60559 Floating-Point option, a domain error shall occur; otherwise, a domain error may occur.
bestie if you're seeing NaN or an infinity go in here, the value coming back is literally unspecified. not a vibe. do not trust it. 🚩

πŸ’€ ERRORS πŸ’€

These functions shall fail if:

  • Domain Error β€” The x argument is NaN or Β±Inf, or the correct value is not representable as an integer.
    • If the integer expression (math_errhandling & MATH_ERRNO) is non-zero, then errno shall be set to [EDOM]. If the integer expression (math_errhandling & MATH_ERREXCEPT) is non-zero, then the invalid floating-point exception shall be raised.

These functions may fail if:

  • Domain Error β€” The correct value is not representable as an integer.
    • If the integer expression (math_errhandling & MATH_ERRNO) is non-zero, then errno shall be set to [EDOM]. If the integer expression (math_errhandling & MATH_ERREXCEPT) is non-zero, then the invalid floating-point exception shall be raised.

The following sections are informative. 🫢 (yes, everything from here down is the chill, non-normative part)


πŸ™ˆ EXAMPLES πŸ™ˆ

None. not a single one 😭 iconic of them honestly.


🌈 APPLICATION USAGE 🌈

On error, the expressions (math_errhandling & MATH_ERRNO) and (math_errhandling & MATH_ERREXCEPT) are independent of each other, but at least one of them must be non-zero. no cap.


πŸ‘‘ RATIONALE πŸ‘‘

These functions differ from the llrint() functions in that the default rounding direction for the llround() functions round halfway cases away from zero and need not raise the inexact floating-point exception for non-integer arguments that round to within the range of the return type. so that's the whole tea: llround is the chaotic one that doesn't care about your rounding direction, and it's not gonna make a whole scene about the inexact exception either. πŸ’…


πŸ¦‹ FUTURE DIRECTIONS πŸ¦‹

None. we're stable, we're thriving, we're not going anywhere. ✨


πŸ”₯ SEE ALSO πŸ”₯

  • feclearexcept()
  • fetestexcept()
  • lround()

The Base Definitions volume of POSIX.1‐2017, Section 4.20, Treatment of Error Conditions for Mathematical Functions, <math.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, 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 .


okay and that's the whole page bestie, that's it, that's the tea πŸ“ this absolute banger was brought to you by IEEE and The Open Group, dated 2017, and honestly? they ate. πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ«ΆπŸ‘‘

πŸ“¦ where this page comes from