diff options
author | David Young <dyoung@hdfgroup.org> | 2020-02-10 23:24:04 (GMT) |
---|---|---|
committer | David Young <dyoung@hdfgroup.org> | 2020-05-11 15:22:24 (GMT) |
commit | c97981da3620cff7f789516dd9dff5ffde86d6d8 (patch) | |
tree | 18bb76ffa9733e713fbc028f2a9cb6cc08c6d760 /test | |
parent | d64afcd9d0ea3be06bb4fefd2d4c1ebd291fef84 (diff) | |
download | hdf5-c97981da3620cff7f789516dd9dff5ffde86d6d8.zip hdf5-c97981da3620cff7f789516dd9dff5ffde86d6d8.tar.gz hdf5-c97981da3620cff7f789516dd9dff5ffde86d6d8.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 'test')
0 files changed, 0 insertions, 0 deletions