Is there any use for C++ throw decoration?

Question

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 throw decoration should do this, like const does for constness of class methods.

Well, it doesn't.

Using throw is still documentary, but may even be dangerously misleading if others think a function cannot throw other exceptions than those listed in its documentation.

Can g++ somehow be persuaded to be more strict on its throw-checking, i.e. really making sure a function decorated as throw() will never-ever throw anything.

Edit: Found this question handling the subject widely.

Answer 1

I would also recommend to look at this essay about the exception specifications. It points out the problems of this C++ feature like:

• It's a shadow type system
• The compiler checks thrown exceptions only at runtime
• The triggered default behavior in the case of a thrown but not specified exception is usually unusable and often misunderstood by the programmers

Answer 2

Basically, the exception specifications are only good as empty exception specification. Otherwise I think they're an experiment that failed. See phlipsy's answer why.

Answer 3

I dont know if the checker/compiler can do that. Perhaps it's just easier to comment it in the function declaration. Well it aint fool proof but if people see that there can be an exception thrown than most of the people will wrap the function call in try and catch.

//Can throw Exception
GetFoo();

Answer 4

It doesn't check compile-time, but a conforming compiler should ensure it at run-time.

If a function throws anything outside of its throw-declaration, the C++ run-time should call std::unexpected, if I recall correctly.