On 22 sep 2011, at 21:04, Don Quixote de la Mancha wrote: > Exceeding the available memory of the garbage collector should not crash, > instead your allocations should fail.
When memory allocations fail, apps crash. Like it or not, that's just the way it is. Not sure what the alternative would be - Changing all (!) of our code to handle out-of-memory errors at every method / function call? And then if you were to catch such an error, having to handle it without being able to allocate memory? I think it's better to just crash in cases such as this one, better to spend time figuring out what the real issue is here, than making it the responsibility of every application developer to figure out how to cope with it. j o a r _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
