• 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: Richard Somers <email@hidden>
  • Date: Thu, 10 Nov 2011 11:21:17 -0700

On Nov 9, 2011, at 12:46 AM, Greg Parker wrote:

> Note that Shuttle missions carried ordinary laptops running ordinary operating systems to do the science work other than flying the spacecraft. The scientists couldn't afford Shuttle-grade development costs nor Shuttle-grade development schedules.

Just a bit of historical trivia. The HP-41C calculator "flew on seven Space Shuttle missions. It could have been used in an emergency to calculate orbit and re-entry information if there were failure of the shuttle main computer systems."

     http://en.wikipedia.org/wiki/HP-41C

Another source indicates that two HP-41C calculators were on board Columbia. One for Center of Gravity and another for Acquisition of Signals.

     http://hpinspace.wordpress.com/category/hp-41/

The HP-41C price at introduction in 1979 was $295 which is a testament to the wonders of capitalism and the free market. I wonder if the Russians are using any iPhones or iPod touches in their functioning space program?

--Richard

_______________________________________________

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:
    • [Moderator] Re: Allocating too much memory kills my App rather than returning NULL
      • From: Scott Anguish <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>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Kyle Sluder <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>)

  • Prev by Date: Re: Allocating too much memory kills my App rather than returning NULL
  • Next by Date: [Moderator] Re: Allocating too much memory kills my App rather than returning NULL
  • Previous by thread: Re: Allocating too much memory kills my App rather than returning NULL
  • Next by thread: [Moderator] Re: Allocating too much memory kills my App rather than returning NULL
  • Index(es):
    • Date
    • Thread