Re: [boost] The noexcept Specifier & Block

Sebastian Redl wrote: [...]

So throw() is deprecated. That doesn't change the fact that its behavior is very similar to what you propose for noexcept.

No, throw() injects catch(...) and I certainly don't want that for noexcept. With or without*** static checking, noexcept specifier is much better than throw(). [...]

I still think that the compile error for noexcept-marked functions is something we definitely want.

So that you can turn such compile errors into undefined behaviour using noexcept blocks or just swallow exceptions? ***) See e.g. http://www.mindview.net/Etc/Discussions/CheckedExceptions regards, alexander.