----- Original Message ----- 
From: "Andreas Huber" <ah2003@[...].net> 
>  E. Gladyshev wrote:
>  > ----- Original Message -----
>  > From: "Andreas Huber" <ah2003@[...].net>
>  >
>  > [...]
>  >> So the library will by default not provide
>  >> any exception handling support (apart from terminating when an action
>  >> throws).
>  >>
>  > I am not sure I understand it.
>  > If there is no any exception handling, how would
>  > the library know when an action throws in order to terminate?
> 
>  I mean that the library will not attempt to catch any exceptions thrown
from
>  actions. Since the state machine could likely be in an unstable state when
>  such an exception is thrown, it must be terminated before the exception is
>  propagated to the client (I'm not doing this with try { ... } catch (
... )
>  { terminate(); }but with a scope guard).
> 

Just to make that I got it right.
There is no guarantee that for an unhandled exception, the scope
guard will do it. Right?
For the scope guard to work, the exception will have to be caught and
the stack unwinding triggered.
So you cannot just say that if an action throws,
the state machine will be terminated.
If the stack unwinding never happens, it is never terminated.
Right?

Eugene

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