Re: Obscure mutex problem

Ulrich Eckhardt wrote:
[...]
It doesn't matter what exception is initially thrown, in the handler it will
be truncated to the baseclass std::exception. Therefore, it will also call
the baseclass' what() function, which won't return the same information as
the one of the exception that was thrown. Yes, you can add all kinds of
handlers for derived exception classes, but what would be the point?

Indeed so. Yup, I'll change that.

[...]
I didn't mean mutexes but the held locks, i.e. lock the mutex in the ctor,
unlock it in the dtor!

Hah! Also a good idea.

Thanks!

--
┌── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─── http://www.cowlark.com ───────────────────
│
│ "There does not now, nor will there ever, exist a programming language in
│ which it is the least bit hard to write bad programs." --- Flon's Axiom
.