Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: c++ exceptions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: c++ exceptions

Subject: Re: c++ exceptions
From: Abdulla Kamar <email@hidden>
Date: Tue, 6 Apr 2010 11:02:21 +1000

Also, in the next standard they're being deprecated (but noexcept is being added):

http://herbsutter.com/2010/03/13/trip-report-march-2010-iso-c-standards-meeting/

On Tue, Apr 6, 2010 at 9:38 AM, Jens Alfke <email@hidden> wrote:

On Apr 5, 2010, at 4:31 PM, Uli Kusterer wrote:

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.

—Jens _______________________________________________

Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

--
Thank you
Abdulla

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References:
	>Re: c++ exceptions (From: Uli Kusterer <email@hidden>)
	>Re: c++ exceptions (From: Jens Alfke <email@hidden>)

Prev by Date: Re: c++ exceptions
Next by Date: Re: c++ exceptions
Previous by thread: Re: c++ exceptions
Next by thread: Re: c++ exceptions
Index(es):
- Date
- Thread