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.
Yes, I asked someone involved in the design of OpenStep.
b.bum
_______________________________________________
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
