summaryrefslogtreecommitdiffstats
path: root/src/H5Dint.c
diff options
context:
space:
mode:
authorDavid Young <dyoung@hdfgroup.org>2020-02-10 23:24:04 (GMT)
committerDavid Young <dyoung@hdfgroup.org>2020-02-10 23:24:04 (GMT)
commit63c95faf49559ea66e3066427961095b69fdb213 (patch)
treefe0d333e1ab8bd344721b00631dd76510207c775 /src/H5Dint.c
parent3109f9e32378087d73fe9b0cd956e41efa1ca6cd (diff)
downloadhdf5-63c95faf49559ea66e3066427961095b69fdb213.zip
hdf5-63c95faf49559ea66e3066427961095b69fdb213.tar.gz
hdf5-63c95faf49559ea66e3066427961095b69fdb213.tar.bz2
Remove tongue-in-cheek credit for Rusty Shackleford and Dale Alvin Gribble.
Delete the comment questioning whether pthread_mutex_lock is allowed in a key destructor, since pthread_key_create(3) provides the answer: There is no notion of a destructor-safe function. If an application does not call pthread_exit() from a signal handler, or if it blocks any signal whose handler may call pthread_exit() while calling async-unsafe functions, all functions may be safely called from destructors. Delete redundant comment.
Diffstat (limited to 'src/H5Dint.c')
0 files changed, 0 insertions, 0 deletions