5
The sad history of the C++ throw(...) exception specifier - The Old New Thing
(devblogs.microsoft.com)
The center for all discussion and news regarding C++.
Why didn't they follow the way Java does it by forcing you to specify all possible throws of a function? Is it because it's too verbose?
Or rather, why isn't nothrow the default unless specified that a function can throw?