Ichthyostega
416895b5b2
The investigation for #1279 leads to the following conclusions - the features and the design of our custom thread-wrapper almost entirely matches the design chosen meanwhile by the C++ committee - the implementation provided by the standard library however uses modern techniques (especially Atomics) and is more precisely worked out than our custom implementation was. - we do not need an *active* threadpool with work-assignment, rather we'll use *active* workers and a *passive* pool, which was easy to implement based on C++17 features ==> decision to drop our POSIX based custom implementation and to retrofit the Thread-wrapper as a drop-in replacement +++ start this refactoring by moving code into the Library +++ create a copy of the Threadwrapper-code to build and test the refactorings while the application itself still uses existing code, until the transition is complete |
||
|---|---|---|
| .. | ||
| gear | ||
| mem | ||
| DIR_INFO | ||
| test-filedescriptors.c | ||
| test-filehandles.c | ||
| test-fileheader.c | ||
| test-filemmap.c | ||
| test-resourcecollector.c | ||
| test-threadpool.c | ||
| test-threads.c | ||