Re: Uncaught exceptions thrown by Cocoa documented anywhere?
Re: Uncaught exceptions thrown by Cocoa documented anywhere?
- Subject: Re: Uncaught exceptions thrown by Cocoa documented anywhere?
- From: Chris Hanson <email@hidden>
- Date: Sat, 16 Feb 2008 01:23:07 -0800
On Feb 15, 2008, at 8:42 PM, Bill Bumgarner wrote:
On Feb 15, 2008, at 7:58 PM, Chris Hanson wrote:
I think this even more than historical legacy is what prevented
OpenStep from being exception-safe at its introduction in 1994;
after all, it had to run reasonably on 25MHz 68040 hardware with
32MB (or even less) memory.
That would be an incorrect assumption.
OpenStep was not "exception-safe" as a conscious design decision.
The designers of the API decided precisely that exceptions would
only be used to encapsulate and indicate non-recoverable,
programmer, type errors.
If the decision had been made to use exceptions as a means of
encapsulating recoverable, user level, errors, then the performance
issues of exception handling would have been addressed in the
compiler and runtime.
That's extremely unfortunate; it means that OpenStep's lack of
exception safety is *not* just an engineering trade-off, but instead
represents a serious design flaw.
At least such things are rare.
-- Chris
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden