Hi Sascha,<br><br><div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>I have a question regarding changing the number of threads:
<br><br>sometimes I need to explicitly kill all worker threads. therefor I set<br>the number of threads to zero using pool::resize(0) and wait for all</blockquote><div><br>[...] <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
since we did not add a task all worker threads are still running<br>(waiting for some work to do). they will be killed as soon as we<br>schedule some tasks.<br>well, this isn't to bad at the first look. </blockquote><div>
I regard this at least as a undesireable behaviour ;-) You may believe it or not: I stumbled about this <br>problem some days ago while refactoring the code (it's not yet commited to CVS).<br><br>A fast fix is to notify&nbsp; m_task_is_available right after 
<br>m_thread_is_idle.notify_all();<br></div>in the resize method.<br><br></div>Best regards,<br>Philipp<br>