J0(3POSIX)

πŸ’– J0 β€” the POSIX girlies' manual, page 3POSIX πŸ’–

okay so bestie, this is J0(3POSIX) from the POSIX Programmer's Manual, and we are about to get so cozy with some Bessel functions. πŸŽ€


🌸 PROLOG 🌸

Real talk first: this page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (so like, go check the corresponding Linux manual page for the deets on Linux behavior), or honestly the interface might not even be implemented on Linux at all. πŸ’€


✨ NAME ✨

j0, j1, jn β€” Bessel functions of the first kind. yes queen, we're doing math. 🧚


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <math.h>

double j0(double x);
double j1(double x);
double jn(int n, double x);

πŸ’… DESCRIPTION πŸ’…

So the j0(), j1(), and jn() functions shall compute Bessel functions of x of the first kind, of orders 0, 1, and n respectively. iconic behavior.

And if your application wants to check for error situations (very responsible of you, love that), you should set errno to zero and call feclearexcept(FE_ALL_EXCEPT) before calling these functions. Then on return, if errno is non-zero, or if fetestexcept(FE_INVALID | FE_DIVBYZERO | FE_OVERFLOW | FE_UNDERFLOW) is non-zero β€” boom, an error has occurred. no cap. 🌈


πŸ‘‘ RETURN VALUE πŸ‘‘

Upon successful completion, these functions shall return the relevant Bessel value of x of the first kind. slay.

If the x argument is too large in magnitude, or the correct result would cause underflow, then 0 shall be returned and a range error may occur. (underflow era, not cute.)

If x is NaN, a NaN shall be returned. it's giving "you get back what you put in" fr fr. 🫢


πŸ’€ ERRORS πŸ’€

These functions may fail if:

  • Range Error β€” the value of x was too large in magnitude, or an underflow occurred.

If the integer expression (math_errhandling & MATH_ERRNO) is non-zero, then errno shall be set to [ERANGE]. And if the integer expression (math_errhandling & MATH_ERREXCEPT) is non-zero, then the underflow floating-point exception shall be raised.

No other errors shall occur. periodt.

The following sections are informative. (translation: the tea is optional but we're still reading it πŸ’–)


πŸ“ EXAMPLES πŸ“

None. (yes really, nothing, the void, empty, we move.)


πŸŽ€ 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. they don't need to match, they just both gotta show up to the function. 😌


⭐ RATIONALE ⭐

None. (the reasoning? not here bestie, we simply don't have one. πŸ¦‹)


πŸ”₯ FUTURE DIRECTIONS πŸ”₯

None. (the future? unclear. we live in the present. πŸ’…)


🌸 SEE ALSO 🌸

  • feclearexcept()
  • fetestexcept()
  • isnan()
  • y0()

And from the Base Definitions volume of POSIX.1‐2017: Section 4.20, Treatment of Error Conditions for Mathematical Functions, and <math.h>. iykyk. ✨


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 .


bestie if anything here looks weird, blame the file conversion, not the math girlies 🫢

and that's the whole page!! mwah πŸ’‹ β€” brought to you by IEEE/The Open Group, 2017, signing off on J0(3POSIX). stay mathematically gorgeous. πŸ’–βœ¨πŸŽ€