
25 Aug
2005
25 Aug
'05
12:12 a.m.
Michael Glassford wrote:
Slawomir Lisznianski wrote:
Hello,
I find the catch(...) clause in the thread_proxy function (thread.cpp) causing more harm than good.
Does anyone have any comments on this? Support or objections?
A good solution is to provide a customization point: call a handler that can be replaced by the user. You then, from a library point of view, have a well-defined behaviour in presence of uncaught exceptions. Then it's possible for the user to "throw;" in order to further propogate the exception (something I would consider evil).
Mike
Ariel.