Improvement to pthread_getspecific(3)
Patrick Kelsey
pkelsey at freebsd.org
Mon May 18 15:23:05 UTC 2015
Hi,
I'd like to make the attached improvement to pthread_getspecific(3), and
this is my first time through a man page edit/commit, so I have a couple of
questions and would like to catch whatever else I'm missing.
1. Attribution - I'm using a lightly edited line from
http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_getspecific.html
(edited to account for the fact that we do not document both
pthread_getspecific() and pthread_setspecific() in the same man page). I'm
assuming that this falls under whatever agreement covers the existing man
page (which was constructed in similar fashion), but there is currently no
attribution in pthread_getspecific(3) and I'm not aware of what agreement
may be in place that allows for this.
2. Markup - should I be using .Pq instead of explicit parentheses?
Thanks,
Patrick
<http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_getspecific.html>
-------------- next part --------------
Index: share/man/man3/pthread_getspecific.3
===================================================================
--- share/man/man3/pthread_getspecific.3 (revision 282933)
+++ share/man/man3/pthread_getspecific.3 (working copy)
@@ -64,6 +64,11 @@
The
.Fn pthread_getspecific
function may be called from a thread-specific data destructor function.
+A call to
+.Fn pthread_getspecific
+for the thread-specific data key being destroyed returns the value NULL,
+unless the value is changed (after the destructor starts) by a call to
+.Fn pthread_setspecific .
.Sh RETURN VALUES
The
.Fn pthread_getspecific
More information about the freebsd-doc
mailing list