Hi, I want to get a deeper understanding of the memory warning handling on iOS in UIViewControllers.
It seems that the default implementation of didReceiveMemoryWarning will set the view to nil, and viewDidUnload gets called. *But* this is only done when the controller implements loadView. Even if this method does nothing at all except calling [super loadView]. What is the reasoning behind making this behavior dependent on the existence of loadView? Also wondering how this is checked, as "respondsToSelector" might not be enough because the superclass implements it anyway? Thanks, Eiko _______________________________________________ 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
