Ichthyostega
81cab9a675
While in principle it would be possible (and desirable) to control worker behaviour exclusively through the Work-Functor's return code, in practice we must concede that Exceptions can always happen from situations beyond our control. And while it is necessary for the WorkForce-dtor to join and block (we can not just pull away the resources from running threads), the same destructor (when called out of order) must somehow be able at least to ask the running threads to terminate. Especially for unit tests this becomes an obnoxious problem -- otherwise each test failure would cause the test runner to hang. Thus adding an emergency halt, and also improve setup for tests with a convenience function to inject a work-function-λ |
||
|---|---|---|
| .. | ||
| gear | ||
| mem | ||
| DIR_INFO | ||
| sync-classlock-test.cpp | ||
| sync-locking-test.cpp | ||
| sync-timedwait-test.cpp | ||
| sync-waiting-test.cpp | ||
| test-filedescriptors.c | ||
| test-filehandles.c | ||
| test-fileheader.c | ||
| test-filemmap.c | ||
| test-resourcecollector.c | ||
| test-threadpool.c | ||
| test-threads.c | ||
| thread-wrapper-join-test.cpp | ||
| thread-wrapper-self-recognition-test.cpp | ||
| thread-wrapper-test.cpp | ||