Might this lock & unlock be there to prevent the destructor from completing until the last timerQueueActive thread has exited? Something like that seems most likely to me from past experience with Jeff's coding style.
Might this lock & unlock be there to prevent the destructor from completing until the last timerQueueActive thread has exited? Something like that seems most likely to me from past experience with Jeff's coding style.