title: Is there any use for C++ throw decoration?
body: <p>I've started using C++ exceptions in a uniform manner, and now I'd like the compiler (g++) to check that there are no "exception leaks". The <code>throw</code> decoration should do this, like <code>const</code> does for constness of class methods.</p>
  
  <p>Well, it doesn't.</p>
  
  <p>Using <code>throw</code> is still documentary, but may even be dangerously misleading if others think a function cannot throw other exceptions than those listed in its documentation.</p>
  
  <p>Can g++ somehow be persuaded to be more strict on its throw-checking, i.e. really making sure a function decorated as <code>throw()</code> will never-ever throw anything.</p>
  
  <p>Edit:
  Found <a href="https://stackoverflow.com/questions/88573/should-i-use-an-exception-specifier-in-c">this question</a> handling the subject widely.</p>