Re: Allocating too much memory kills my App rather than returning NULL
Re: Allocating too much memory kills my App rather than returning NULL
- Subject: Re: Allocating too much memory kills my App rather than returning NULL
- From: Kyle Sluder <email@hidden>
- Date: Tue, 08 Nov 2011 22:49:15 -0800
On Tue, Nov 8, 2011 at 10:44 PM, Don Quixote de la Mancha
<email@hidden> wrote:
> On Tue, Nov 8, 2011 at 9:48 PM, Wade Tregaskis <email@hidden> wrote:
>>> Simple as that, eh? Being able to gracefully handle all out of memory situations to me seems as "simple" as being required to treat every single method / function call as potentially raising an exception, and requiring the developer to add handlers + cleanup code. No existing code (OS or apps) is exceptions safe at every single line of source code. At the very least this would require a complete rewrite / review of every single line of existing source code in both OS and apps, something that seems neither simple nor practical to me.
>
> Kids These Days.
>
> While the Space Shuttle exploded twice, I hasten to point out that
> neither of those failures was due to software bugs.
The Shuttle's software was a closed real-time system written entirely
by one team within NASA that followed incredibly strict code-auditing
and development procedures. We studied it in college.
If you tried to follow the NASA's development methodology, your
competitors would eat your breakfast, lunch, and dinner before you
shipped v1.0.
--Kyle Sluder
_______________________________________________
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