On Tue, Nov 25, 2008 at 4:40 PM, Peter Dimov <pdimov@pdimov.com> wrote:
Emil Dotchevski:
So the question is what's better for boost::thread, to conform to the C++ standard -- which in the scenario I outlined and Dave had in mind can only be done using catch(...) -- or to leave conformance up to the compiler, meaning terminate() may not be called when it should, but assuming that that is a bug (which may not be the case, as Dave pointed out) you'll get a better error message.
This is a false dilemma. There is a third option: use catch(...) only when the compiler doesn't call terminate() itself.
Naturally -- why'd boost::thread use catch(...) otherwise? To call terminate() "better"? :) Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode