7ee Subj : Re: recursive mutexes To : comp.programming.threads From : doug Date : Tue May 17 2005 09:29 pm "David Butenhof" wrote in message news:8erie.5568$FJ4.1906@news.cpqcorp.net... > Dragan Cvetkovic wrote: >> David Butenhof writes: > >> [snip of the excellent description of recursive mutex history] > > Thanks. For the "excellent", that is, not for the "snip". ;-) > >>>Recursive mutexes can be a great tool for prototyping thread support in >>>an >>>existing library, exactly because it lets you defer the hard part: the >>>call >>>path and data dependency analysis of the library. But for that same >>>reason, >>>always remember that you're not DONE until they're all gone, so you can >>>produce a library you're proud of, that won't unnecessarily contrain the >>>concurrency of the entire application. >>> >>>Or sit back and let someone else do the design. >> >> Dave, you should collect all these essays of yours posted to c.p.t and >> publish the (long awaited) second edition of your book around it :-) > > You know, I actually got bugged by an editor at A-W a week or so ago, and > I really am thinking about it. I just need to survive this bloody HP-UX > release and get some time to come up for air. (It's been rare that I find > time even to skim through the newsgroup in the past few months, but I do > miss it. ;-) ) > > On the other hand, while I've had fun writing long POSIX reminiscences, I > could probably fill a whole book just with that, nevermind fitting in > actual information. Might be fun... but would it sell? I'm not quite old > enough to call it "Musings of a Threads Curmudgeon" (and anyway I'd > already bestowed that title on a previous manager). I'd buy it... > > -- > Dave Butenhof, David.Butenhof@hp.com > HP Utility Pricing software, POSIX thread consultant > Manageability Solutions Lab (MSL), Hewlett-Packard Company > 110 Spit Brook Road, ZK2/3-Q18, Nashua, NH 03062 . 0