From: "ara.t.howard" Date: 2008-01-02T06:33:13+09:00 Subject: Re: deadlock in ThreadPool using backtick On Dec 31, 2007, at 4:44 PM, Charles Oliver Nutter wrote: > > Yes, what you pointed out is completely busted. I hadn't seen that > code. But why would you spin things off into a bunch of processes? > Just fixing shutdown should make it work fine, if backticks aren't > the problem. you could just fix shutdown to be sure. but the way i think is that i'd be right back in the hot seat when it came time to implement #pause and #start, etc. condition vars are, to me, just code smell - they're asking for trouble. the other reason is that, to me, the name 'ThreadPool' suggests a pool of threads, not a stack of ever changing threads. so, in much the same way as i'd expect something called 'ConnectionPool' to reuse connections i except a thread pool to reuse a few threads. that's reading into the code i realize - but that's my personal through process. as you well know there are always many ways to skin a cat. kind regards. a @ http://codeforpeople.com/ -- we can deny everything, except that we have the possibility of being better. simply reflect on that. h.h. the 14th dalai lama