🚀 go-pugleaf

Dave Butenhof wrote:

> Having classes with destructors that clean up state, as TRIVIALLY
> DEMONSTRATED by Locker, is clearly the best way to apply C++ semantics to
> the problem of protecting thread state invariants against "unusual"
> routine exit. But the true solution in nearly all cases must go beyond
> the triviality of Locker to restore data invariants, not merely the state
> of the mutex!

So I guess we all agree.  The original question was a pretty vague
one, and my response was therefore generic.  When you apply generic
techniques, a "cookbook" approach doesn't work.  I did what I could
to make that clear, but in the discussion all of the original context
was lost.  Part of the peril of being taken out of context!
-- 
David Brownell <brownell@ix.netcom.com>