throw without arguments for failure signalling
<p>Is it ok to just call <code>throw;</code> from constructor if something goes awry, and you have no idea how to recover?</p>

<p>The idea is to let the app crash with a dump, as the state is unknown. Or should you always specify an argument?</p>

<p>From MSDN I only found that it rethrows if there is no argument, but no idea what happens if there is no initial exception to rethrow.</p>
