Mind if I add this as a bug against thread? Jim
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of dizzy Sent: 02 May 2008 08:15 To: boost@lists.boost.org Subject: Re: [boost] Why does boost::thread::thread_start_function havecatch(...)? (Win32)
On Thursday 01 May 2008 13:23:35 James Talbut wrote:
By calling std::terminate in the catch handler we lose the JIT debugger - and thus information about what the exception is that we haven't caught. Without the catch the process is still going to be killed, so what's the benefit of having that?
Probably because not all implementations can allow threads to exit properly with an exception (since that is an area completely uncovered by the current C++ standard, along with threading in general). But I agree, that where possible it should not have a catch(...) and it should behave like exiting from main() with an exception behaves (and if your implementation does not make this behaviour the same then bad luck).
-- Mihai RUSU Email: dizzy@roedu.net "Linux is obsolete" -- AST _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
________________________________________________________________________ This e-mail, and any attachment, is confidential. If you have received it in error, do not use or disclose the information in any way, notify me immediately, and please delete it from your system. ________________________________________________________________________