Hello *,<br><br>I have a question regarding the tools BOOST_&lt;level&gt;_THROW:<br><br>Why is it required to specify the exception being thrown? What if I don&#39;t know which exception is thrown, but I know that it should be thrown?<br>
<br>My use case is:<br><br>I have a worker class which executes some functionality. I know that the functionality will throw, but I would like to test that my class will remain in the consistent state after the exception was thrown? With BOOST_&lt;level&gt;_THROW(class_inst.execute()) I could spare the try{}catch(...){} block and make other test assertions, but unfortunately it is not possible, due to lacking of this utility.<br>
<br>I would propose a throw guard into the lib, which does not produce any assertion, but swallows an exception. My intention is:<br>I have to develop inside of a huge framework. The functionality I am trying to execute will only work on a target hardware. Since I am inside a debugger and not going to test the the executed functionality itself, but check the state of my class I think such a tool might help.<br>
<br>With Kind Regards,<br>Ovanes<br>