I would like to understand why it could be useful to do this (assuming “object” was previously allocated):
[object release];
object=nil;
Thx for helping,
Stephane
I would like to understand why it could be useful to do this (assuming
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.
I would like to understand why it could be useful to do this (assuming “object” was previously allocated):
[object release];
object=nil;
Thx for helping,
Stephane
Even though you release an object, your variable will still point to something. What it points to is undefined. It could still point to the old object, or to some point in memory. Setting it to nil avoids sending messages to whatever it points to, and prevents errors (messaging nil does nothing).
Here’s an answer that states it better: Setting pointers to nil, objective-c