On Wednesday 09 November 2011 10:36:32 TONGARI wrote:
2011/11/9 Oliver Kowalke <oliver.kowalke@gmx.de>
ex_unwind_stack is swallowed by boost::context - it is required in order to implement expilict stack unwinding. It is important that the user dosn't swallow this exception! I think the best would be that the user dosn't know the type of this exception (unnamed exception?) - not sure if I should supress this info or note it explicitly in the docu.
Indeed the user should not swallow it, but there's no reason to prohibit the user from using catch(...) as well, so why not let the user catch and rethrow ex_unwind_stack explicitly for stack unwinding?
actually "catch(...)" not followed by "throw;" just causes lots of other problems (see for example http://udrepper.livejournal.com/21541.html) so that it should indeed be considered prohibited on a general basis Helge