PTHREAD_SETSPECIFIC(3P)

✨ PROLOG ✨

okay so before we even get into it β€” this page is part of the POSIX Programmer's Manual πŸ’– that's the whole vibe. but heads up bestie: 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. πŸ™ˆ no cap.


🌸 NAME 🌸

pthread_setspecific β€” thread-specific data management 🧡✨


πŸŽ€ SYNOPSIS πŸŽ€

#include <pthread.h>

int pthread_setspecific(pthread_key_t key, const void *value);

πŸ’… DESCRIPTION πŸ’…

bestie, this one's a redirect β€” you gotta refer to pthread_getspecific(). it's giving "go ask my sibling, they have the whole story" 🫢


okay legal moment, we have to do this, stay with me πŸ’œ

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. 🫑

and if there's ever any discrepancy between this version and the original IEEE and The Open Group Standard, then the original IEEE and The Open Group Standard is the referee document β€” it's the main character, this page is just the understudy. 🎭 the original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

also, any typographical or formatting errors that show up in this page are most likely to have been introduced during the conversion of the source files to man page format 😭 (not our fault, fr fr). to report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .


that's the whole page, you ate that, periodt βœ¨πŸ’– and for the record, this was brought to you by IEEE/The Open Group, 2017, filed under PTHREAD_SETSPECIFIC(3P) β€” mwah, bye bestie! πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from