this post was submitted on 19 Jun 2023
5 points (85.7% liked)

C++

1783 readers
1 users here now

The center for all discussion and news regarding C++.

Rules

founded 1 year ago
MODERATORS
lysdexic
[email protected]
Nihili0
5
The sad history of the C++ throw(...) exception specifier - The Old New Thing (devblogs.microsoft.com)
submitted 1 year ago by [email protected] to c/cpp
1 comments fedilink hide all child comments
 

Although throw() has been deprecated for a while now, I thought this was an interesting bit of history regarding Microsoft's compiler.

you are viewing a single comment's thread
view the rest of the comments
[–] jormaig 1 points 1 year ago

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?