Does NSAutoreleasePool also covers variables in all the called methods?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If that’s the only place where
-isNotExpiredis called, the auto release pool you’ve set up will contain objects autoreleased in-isNotExpired(including startDate).Note that in a normal Cocoa application,
NSApplicationMain()called inmain()in main.m will create an autorelease pool for you, so this code wouldn’t leak anyway. You generally only create your own autorelease pool in cases where you’ll be generating lots of temporary objects with a short useful life (in a loop for instance) and want to keep your high water memory usage down.