[boost] Re: Re: Boost.threads: interthread exception conveyance

From: Eric Woodruff (Eric.Woodruff_at_[hidden])
Date: 2002-08-24 11:41:04

It doesn't return. (In the case of the no_exceptions policy, the application
has terminated anyway.) That is not to say that threads with no return type
cannot or should not propagate exceptions. I understand that some rely on
the fact that join () returns a value to assume that the user will put a
proper try/catch around it -- or even call join () to not let the exception
die. But it is still a user responsibility and the user can choose to throw
exceptions why any return type.

----- Original Message -----
From: Peter Dimov
Newsgroups: gmane.comp.lib.boost.devel
Sent: Saturday, 2002:August:24 12:19
Subject: Re: Re: Boost.threads: interthread exception conveyance

From: "Eric Woodruff" <Eric.Woodruff_at_[hidden]>
> ">   q19) In reality why wouldn't q5's technique for handling an uncaught
> exception thrown in a nonjoinable t apply equally well to handling an
> uncaught exception thrown in a joinable t as well?  (Why have two
techniques
> instead of one?)<
>
> To support threads that are able to return a value."
>
> The threads can support return values without exceptions, they are
> orthogonal, but necessary, concepts.

What value do you return when the thread function has ended with an
exception?

_______________________________________________
Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost