• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Allocating too much memory kills my App rather than returning NULL
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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: Jean-Daniel Dupas <email@hidden>
  • Date: Wed, 09 Nov 2011 10:02:50 +0100

Le 9 nov. 2011 à 07:44, Don Quixote de la Mancha a écrit :

> 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.
>

No, but Ariane 5 first launch failure was ;-)


-- Jean-Daniel




_______________________________________________

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

  • Follow-Ups:
    • Re: Allocating too much memory kills my App rather than returning NULL
      • From: Don Quixote de la Mancha <email@hidden>
References: 
 >Allocating too much memory kills my App rather than returning NULL (From: Don Quixote de la Mancha <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Jens Alfke <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Don Quixote de la Mancha <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Greg Parker <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Wade Tregaskis <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Joar Wingfors <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Wade Tregaskis <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Don Quixote de la Mancha <email@hidden>)

  • Prev by Date: Re: ObjC's flat and all-exported namespace, help!
  • Next by Date: Re: NSFileHandle readInBackground vs threading?
  • Previous by thread: [Moderator] Re: Allocating too much memory kills my App rather than returning NULL
  • Next by thread: Re: Allocating too much memory kills my App rather than returning NULL
  • Index(es):
    • Date
    • Thread