MirBSD manpage: pthread_key_delete(3)

PTHREAD_KEY_DELETE(3)      BSD Programmer's Manual       PTHREAD_KEY_DELETE(3)


     pthread_key_delete - delete a thread-specific data key


     #include <pthread.h>

     pthread_key_delete(pthread_key_t key);


     The pthread_key_delete() function deletes a thread-specific data key pre-
     viously returned by pthread_key_create(). The thread-specific data values
     associated with key need not be NULL at the time that
     pthread_key_delete() is called. It is the responsibility of the applica-
     tion to free any application storage or perform any cleanup actions for
     data structures related to the deleted key or associated thread-specific
     data in any threads; this cleanup can be done either before or after
     pthread_key_delete() is called. Any attempt to use key following the call
     to pthread_key_delete() results in undefined behavior.

     The pthread_key_delete() function is callable from within destructor
     functions. Destructor functions are not invoked by pthread_key_delete().
     Any destructor function that may have been associated with key will no
     longer be called upon thread exit.


     If successful, the pthread_key_delete() function will return zero. Other-
     wise an error number will be returned to indicate the error.


     pthread_key_delete() will fail if:

     [EINVAL]      The key value is invalid.


     pthread_getspecific(3), pthread_key_create(3), pthread_setspecific(3)


     pthread_key_delete() conforms to ISO/IEC 9945-1:1996 ("POSIX.1").

MirBSD #10-current              April 4, 1996                                1

Generated on 2022-12-24 01:00:14 by $MirOS: src/scripts/roff2htm,v 1.113 2022/12/21 23:14:31 tg Exp $ — This product includes material provided by mirabilos.

These manual pages and other documentation are copyrighted by their respective writers; their sources are available at the project’s CVSweb, AnonCVS and other mirrors. The rest is Copyright © 2002–2022 MirBSD.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report — diffs preferred.

Kontakt / Impressum & Datenschutzerklärung