diff options
author | David Young <dyoung@hdfgroup.org> | 2020-02-10 23:24:04 (GMT) |
---|---|---|
committer | David Young <dyoung@hdfgroup.org> | 2020-02-10 23:24:04 (GMT) |
commit | 63c95faf49559ea66e3066427961095b69fdb213 (patch) | |
tree | fe0d333e1ab8bd344721b00631dd76510207c775 /tools/testfiles/tref-escapes-at.h5 | |
parent | 3109f9e32378087d73fe9b0cd956e41efa1ca6cd (diff) | |
download | hdf5-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 'tools/testfiles/tref-escapes-at.h5')
0 files changed, 0 insertions, 0 deletions