[apple/libc.git] / pthreads / pthread_key_create.3

.\" Copyright (c) 1996 John Birrell <jb@cimlogic.com.au>.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\"    notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\"    notice, this list of conditions and the following disclaimer in the
.\"    documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\"    must display the following acknowledgement:
.\"	This product includes software developed by John Birrell.
.\" 4. Neither the name of the author nor the names of any co-contributors
.\"    may be used to endorse or promote products derived from this software
.\"    without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY JOHN BIRRELL AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\" $FreeBSD: src/lib/libc_r/man/pthread_key_create.3,v 1.6.2.4 2001/08/17 15:42:51 ru Exp $
.\"
.Dd April 4, 1996
.Dt PTHREAD_KEY_CREATE 3
.Os
.Sh NAME
.Nm pthread_key_create
.Nd thread-specific data key creation
.Sh SYNOPSIS
.Fd #include <pthread.h>
.Ft int
.Fo pthread_key_create
.Fa "pthread_key_t *key"
.Fa "void (*destructor)(void *)"
.Fc
.Sh DESCRIPTION
The
.Fn pthread_key_create
function creates a thread-specific data key
that is visible to all threads in the process.
Key values provided by
.Fn pthread_key_create
are opaque objects, used to locate thread-specific data.
Although the same
key value may be used by different threads, the values bound to the key
by
.Fn pthread_setspecific
are maintained on a per-thread basis and persist for the life of the calling
thread.
.Pp
Upon key creation, the value NULL is associated with the new key in all
active threads.
Upon thread creation, the value NULL is associated with all
defined keys in the new thread.
.Pp
An optional destructor function may be associated with each key value.
At
thread exit, if a key value has a non-NULL destructor pointer, and the
thread has a non-NULL value associated with the key, the function pointed
to is called with the current associated value as its sole argument.
The
order of destructor calls is unspecified if more than one destructor exists
for a thread when it exits.
.Pp
If, after all the destructors have been called for all non-NULL values
with associated destructors, there are still some non-NULL values with
associated destructors, then the process is repeated.
If, after at least
[PTHREAD_DESTRUCTOR_ITERATIONS] iterations of destructor calls for
outstanding non-NULL values, there are still some non-NULL values with
associated destructors, the implementation stops calling destructors.
.Sh RETURN VALUES
If successful, the
.Fn pthread_key_create
function will store the newly created key value at the location specified by
.Fa key
and returns zero.
Otherwise, an error number will be returned to indicate
the error.
.Sh ERRORS
.Fn pthread_key_create
will fail if:
.Bl -tag -width Er
.It Bq Er EAGAIN
The system lacked the necessary resources to create another thread-specific
data key, or the system-imposed limit on the total number of keys per process
[PTHREAD_KEYS_MAX] would be exceeded.
.It Bq Er ENOMEM
Insufficient memory exists to create the key.
.El
.Sh SEE ALSO
.Xr pthread_getspecific 3 ,
.Xr pthread_key_delete 3 ,
.Xr pthread_setspecific 3
.Sh STANDARDS
.Fn pthread_key_create
conforms to
.St -p1003.1-96 .
Commit	Line	Data
5b2abdfb A	1	.\" Copyright (c) 1996 John Birrell <jb@cimlogic.com.au>.
	2	.\" All rights reserved.
	3	.\"
	4	.\" Redistribution and use in source and binary forms, with or without
	5	.\" modification, are permitted provided that the following conditions
	6	.\" are met:
	7	.\" 1. Redistributions of source code must retain the above copyright
	8	.\" notice, this list of conditions and the following disclaimer.
	9	.\" 2. Redistributions in binary form must reproduce the above copyright
	10	.\" notice, this list of conditions and the following disclaimer in the
	11	.\" documentation and/or other materials provided with the distribution.
	12	.\" 3. All advertising materials mentioning features or use of this software
	13	.\" must display the following acknowledgement:
	14	.\" This product includes software developed by John Birrell.
	15	.\" 4. Neither the name of the author nor the names of any co-contributors
	16	.\" may be used to endorse or promote products derived from this software
	17	.\" without specific prior written permission.
	18	.\"
	19	.\" THIS SOFTWARE IS PROVIDED BY JOHN BIRRELL AND CONTRIBUTORS ``AS IS'' AND
	20	.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
	21	.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
	22	.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
	23	.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
	24	.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
	25	.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
	26	.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
	27	.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
	28	.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
	29	.\" SUCH DAMAGE.
	30	.\"
	31	.\" $FreeBSD: src/lib/libc_r/man/pthread_key_create.3,v 1.6.2.4 2001/08/17 15:42:51 ru Exp $
	32	.\"
	33	.Dd April 4, 1996
	34	.Dt PTHREAD_KEY_CREATE 3
	35	.Os
	36	.Sh NAME
	37	.Nm pthread_key_create
	38	.Nd thread-specific data key creation
	39	.Sh SYNOPSIS
	40	.Fd #include <pthread.h>
	41	.Ft int
224c7076 A	42	.Fo pthread_key_create
	43	.Fa "pthread_key_t *key"
	44	.Fa "void (destructor)(void )"
	45	.Fc
5b2abdfb A	46	.Sh DESCRIPTION
	47	The
	48	.Fn pthread_key_create
224c7076 A	49	function creates a thread-specific data key
224c7076 A	50	that is visible to all threads in the process.
5b2abdfb A	51	Key values provided by
5b2abdfb A	52	.Fn pthread_key_create
224c7076	53	are opaque objects, used to locate thread-specific data.
5b2abdfb A	54	Although the same
	55	key value may be used by different threads, the values bound to the key
	56	by
	57	.Fn pthread_setspecific
	58	are maintained on a per-thread basis and persist for the life of the calling
	59	thread.
	60	.Pp
	61	Upon key creation, the value NULL is associated with the new key in all
	62	active threads.
	63	Upon thread creation, the value NULL is associated with all
	64	defined keys in the new thread.
	65	.Pp
	66	An optional destructor function may be associated with each key value.
	67	At
	68	thread exit, if a key value has a non-NULL destructor pointer, and the
	69	thread has a non-NULL value associated with the key, the function pointed
	70	to is called with the current associated value as its sole argument.
	71	The
	72	order of destructor calls is unspecified if more than one destructor exists
	73	for a thread when it exits.
	74	.Pp
	75	If, after all the destructors have been called for all non-NULL values
	76	with associated destructors, there are still some non-NULL values with
	77	associated destructors, then the process is repeated.
	78	If, after at least
	79	[PTHREAD_DESTRUCTOR_ITERATIONS] iterations of destructor calls for
	80	outstanding non-NULL values, there are still some non-NULL values with
	81	associated destructors, the implementation stops calling destructors.
	82	.Sh RETURN VALUES
	83	If successful, the
	84	.Fn pthread_key_create
	85	function will store the newly created key value at the location specified by
	86	.Fa key
	87	and returns zero.
224c7076	88	Otherwise, an error number will be returned to indicate
5b2abdfb A	89	the error.
	90	.Sh ERRORS
	91	.Fn pthread_key_create
	92	will fail if:
	93	.Bl -tag -width Er
	94	.It Bq Er EAGAIN
	95	The system lacked the necessary resources to create another thread-specific
	96	data key, or the system-imposed limit on the total number of keys per process
	97	[PTHREAD_KEYS_MAX] would be exceeded.
	98	.It Bq Er ENOMEM
	99	Insufficient memory exists to create the key.
	100	.El
	101	.Sh SEE ALSO
	102	.Xr pthread_getspecific 3 ,
	103	.Xr pthread_key_delete 3 ,
	104	.Xr pthread_setspecific 3
	105	.Sh STANDARDS
	106	.Fn pthread_key_create
	107	conforms to
	108	.St -p1003.1-96 .