RINT(3P)
πΈ RINT(3P) β bestie edition πΈ
okay so this is the POSIX Programmer's Manual page for rint, and I'm gonna walk you through it like we're texting at 1am, except every single fact stays exactly where it was. π
β¨ PROLOG β¨
real talk before we even start: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ β so like, go consult the corresponding Linux manual page for the tea on Linux behavior. Orβ¦ it might not be implemented on Linux at all. π iykyk.
π NAME π
rint, rintf, rintl β round-to-nearest integral value. that's the whole vibe, bestie. β¨
π SYNOPSIS π
#include <math.h>
double rint(double x);
float rintf(float x);
long double rintl(long double x);
three icons, three types, one job. π
π¦ DESCRIPTION π¦
okay so the functionality described on this reference page is aligned with the ISO C standard. And like, any conflict between the requirements described here and the ISO C standard? Not intentional, promise. This volume of POSIX.1β2017 defers to the ISO C standard. periodt.
These functions shall return the integral value (represented as a double) nearest x in the direction of the current rounding mode. The current rounding mode is implementation-defined β so it's giving "mystery, but make it standards-compliant." π§
Now here's the mood board of rounding modes, bestie:
- If the current rounding mode rounds toward negative infinity, then
rint()shall be equivalent tofloor(). - If the current rounding mode rounds toward positive infinity, then
rint()shall be equivalent toceil(). - If the current rounding mode rounds towards zero, then
rint()shall be equivalent totrunc(). - If the current rounding mode rounds towards nearest, then
rint()differs fromround()in that halfway cases are rounded to even rather than away from zero. (banker's rounding ate, ngl)
These functions differ from the nearbyint(), nearbyintf(), and nearbyintl() functions only in that they may raise the inexact floating-point exception if the result differs in value from the argument. so like, cousins, not twins. π―
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. write that down. π
π RETURN VALUE π
Upon successful completion, these functions shall return the integer (represented as a double precision number) nearest x in the direction of the current rounding mode. The result shall have the same sign as x. slay.
- If
xis NaN, a NaN shall be returned. - If
xis Β±0 or Β±Inf,xshall be returned. (it said "no notes, I'm already perfect" π )
π ERRORS π
No errors are defined. iconic behavior honestly.
The following sections are informative. π«Ά
π EXAMPLES π
None. bestie we have no examples. we ball regardless.
π APPLICATION USAGE π
The integral value returned by these functions need not be expressible as an intmax_t.
The return value should be tested before assigning it to an integer type to avoid the undefined results of an integer overflow. π this is the part where you do NOT just yolo it into an int, okay? test first.
π§ RATIONALE π§
None. no thoughts, head empty, standard approved.
β FUTURE DIRECTIONS β
None. the future is unspecified and honestly? that's her main character energy.
π₯ SEE ALSO π₯
abs()ceil()feclearexcept()fetestexcept()floor()isnan()nearbyint()
The Base Definitions volume of POSIX.1β2017, Section 4.20, Treatment of Error Conditions for Mathematical Functions, <math.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 .
okay that's the whole page, you ate that, go round some numbers responsibly π«Άβ¨
β brought to you by IEEE/The Open Group, 2017, aka the year this page was born. RINT(3P) signing off π π
π¦ where this page comes from
- alpine 3.22: man-pages-posix 2017a-r0 Β· custom
- alpine 3.23: man-pages-posix 2017a-r0 Β· custom
- alpine 3.24: man-pages-posix 2017a-r0 Β· custom
- arch rolling: man-pages 6.19-1
- arch rolling: man-pages 6.20-1 Β· BSD-2-Clause AND BSD-3-Clause AND BSD-4.3TAHOE AND BSD-4-Clause-UC AND GPL-1.0-or-later AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND LGPL-3.0-linking-exception AND LGPL-3.0-or-later AND LicenseRef-Public-Domain AND LicenseRef-UltraPermissive AND Linux-man-pages-1-para AND Linux-man-pages-copyleft AND Linux-man-pages-copyleft-2-para AND Linux-man-pages-copyleft-var AND MIT AND Spencer-94
- nixpkgs unstable: man-pages-posix 2017a
- opensuse-leap 16.0: man-pages-posix 2017a-160000.4.1 Β· SUSE-IEEE
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms