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 am creating an NSArray from a URL that points to a plist
NSLog(@"_url rc:[%d]",[_url retainCount]); //prints "_url rc:[1]"
content = [NSArray arrayWithContentsOfURL:_url];
NSLog(@"_url rc:[%d]",[_url retainCount]); //prints "_url rc:[10]"
I’m completely at a loss as to why this is occurring. Let me know if you need further information.
Do not call -retainCount.
The absolute retain count of an object is useless unless your code is the only thing that has ever touched the object. As soon as you pass the object through system API’s the absolute retain count is no longer something you have any control over.
As chrissr implied, the retain count of an object should be treated entirely as a delta. If you cause it to be increased, you should cause it to be decreased. If you retain, you must release. If you copy, you must release. Etc…