Skip to content

Commit b7e42fe

Browse files
committed
specify when destructors are called
1 parent 166846a commit b7e42fe

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

threads.tex

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -546,12 +546,12 @@
546546
place per thread with minimal changes to the original code.
547547
\item When you create a key, the \texttt{NULL} value is associated with it.
548548
\item If you do not need the destructor function, use \texttt{NULL}.
549-
\item Destructors are called in unspecified order on all keys with a value
550-
different from \texttt{NULL}. Its value is set to \texttt{NULL} and the
551-
original value is used as a parameter to the destructor. If, after all the
552-
destructors have been called for all non-\texttt{NULL} values with associated
553-
destructors, there are still some non-\texttt{NULL} values with associated
554-
destructors, then the process is repeated. If, after at least
549+
\item Destructors are called at thread exit in unspecified order on all keys
550+
with a value different from \texttt{NULL}. Its value is set to \texttt{NULL}
551+
and the original value is used as a parameter to the destructor. If, after
552+
all the destructors have been called for all non-\texttt{NULL} values with
553+
associated destructors, there are still some non-\texttt{NULL} values with
554+
associated destructors, then the process is repeated. If, after at least
555555
\texttt{PTHREAD\_DESTRUCTOR\_ITERATIONS} iterations of destructor calls for
556556
outstanding non-NULL values, there are still some non-\texttt{NULL} values with
557557
associated destructors, the implementation may (it usually does otherwise you

0 commit comments

Comments
 (0)