Sorry, wrote some thing wrong. Please read further...<br><br><div class="gmail_quote">On Thu, Feb 28, 2008 at 7:29 PM, Ovanes Markarian &lt;<a href="mailto:om_boost@keywallet.com">om_boost@keywallet.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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 --&gt;inside a debugger&lt;--</blockquote>
<div>&nbsp;&nbsp; should be: since I am not testing on a target platform<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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><font color="#888888">Ovanes<br>
</font></blockquote></div><br>