setjmp.h(7POSIX)

πŸ’– setjmp.h β€” stack environment declarations πŸ’–

okay so bestie, welcome to setjmp.h(7POSIX) β€” yeah it's the POSIX Programmer's Manual, and she's iconic. πŸŽ€


✨ PROLOG ✨

so like, real talk before we get into it: this manual page is part of the POSIX Programmer's Manual. the Linux implementation of this interface may differ (so go check the corresponding Linux manual page for the deets, fr fr), or β€” plot twist β€” the interface might just not be implemented on Linux at all. πŸ’€


🌸 NAME 🌸

setjmp.h β€” stack environment declarations. she's giving "jumping around the stack" energy, no cap.


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <setjmp.h>

that's it. that's the whole vibe. 🫢


πŸ‘‘ DESCRIPTION πŸ‘‘

okay so some of the functionality described on this reference page extends the ISO C standard. meaning: applications shall define the appropriate feature test macro (peep the System Interfaces volume of POSIX.1‐2017, Section 2.2, The Compilation Environment) to enable the visibility of these symbols in this header. iykyk. ✨

the <setjmp.h> header shall define the array types jmp_buf and sigjmp_buf. slay.

the following shall be declared as functions and may also be defined as macros. function prototypes shall be provided. periodt.

void   _longjmp(jmp_buf, int);
void   longjmp(jmp_buf, int);
void   siglongjmp(sigjmp_buf, int);

the following may be declared as functions, or defined as macros, or both. if functions are declared, function prototypes shall be provided. flexible queen. πŸ’…

int    _setjmp(jmp_buf);
int    setjmp(jmp_buf);
int    sigsetjmp(sigjmp_buf, int);

ngl the following sections are informative β€” that's literally the whole tea, no more, no less.


πŸ’œ APPLICATION USAGE πŸ’œ

None.

like. none. nothing. the void. 😭


🧚 RATIONALE 🧚

None.

she said "no thoughts, head empty" and honestly? respect. πŸ™ˆ


πŸ“ FUTURE DIRECTIONS πŸ“

None.

no plans, no drama, just vibes. ⭐


πŸ”₯ SEE ALSO πŸ”₯

  • The System Interfaces volume of POSIX.1‐2017, Section 2.2, The Compilation Environment
  • _longjmp()
  • longjmp()
  • setjmp()
  • siglongjmp()
  • sigsetjmp()

go read those too, bestie, they're the main characters of this whole jumping-around situation. 🌈


so here's the serious bit, and we're keeping it 100:

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 one lil heads-up: the prolog thing about Linux implementations differing or straight-up not existing? that's a real caveat, not a bit. check your platform, bestie. 🫢

and that's the whole page!! mwah. this was IEEE/The Open Group, 2017, page setjmp.h(7POSIX) β€” tysm for reading, ily, go define your feature test macros πŸ’–βœ¨πŸŽ€