Cocoa-Touch: memory management?

In fact, it was exactly this use case that was the motivation behind inventing NSAutoreleasePool. – Dave DeLong Oct 8 '09 at 19:00.

I think the convention is to autorelease it in the alloc statement: UILabel *l = UILabel alloc initWithFrame:CGRectMake(0, 0, 300, 44) autorelease; Since you need the object to exist after the method exits, you have no choice but to use autorelease. Typically, you need to make sure in the calling method that you retain a copy, or it could be released on you randomly. In this case, the pickerView does this for you, so no worries.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.