site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Apr 5, 2010, at 4:31 PM, Uli Kusterer wrote: —Jens _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... C++ supports throw specifiers, too, for both functions and methods. It's just that the defaults are different: If you don't specify a throw specifier, it will let you throw *any* exception. But IIRC, the specifiers are enforced at runtime, not compile time. So if I declare a function as "throw ()", i.e. not allowed to throw anything, it's still allowed to call functions that can throw exceptions. It's just that if an exception actually gets thrown, it'll cause the program to abort. This is IMHO not nearly as useful as detecting exception violations at compile time. This email sent to site_archiver@lists.apple.com