How to know if an object is autoreleased or not?

Basically, if you init copy or retain an object you are responsible for releasing it. If you don't, you are not responsible for releasing it URL1 Many classes provide methods of the form +className... that you can use to obtain a new instance of the class. Often referred to as “convenience constructors�

, these methods create a new instance of the class, initialize it, and return it for you to use. Although you might think you are responsible for releasing objects created in this manner, that is not the case according to the ownership policy set out earlier. Because the class creates the new object, it is responsible for disposing of the new object.

Basically, if you init, copy, or retain an object you are responsible for releasing it. If you don't, you are not responsible for releasing it. URL1 Many classes provide methods of the form +className... that you can use to obtain a new instance of the class.

Often referred to as “convenience constructors� , these methods create a new instance of the class, initialize it, and return it for you to use. Although you might think you are responsible for releasing objects created in this manner, that is not the case according to the ownership policy set out earlier.

Because the class creates the new object, it is responsible for disposing of the new object.

This is a good answer too. – bobobobo Nov 10 '09 at 4:11.

The method signature itself tells you. The pattern to methods with signatures like "classNameWithData:data1:data2" is to return an alloc/init/autorelease instance of that thing. They are conveniences there so that you don't have to do it.

If you do not want an autorelease version of something, then do not instantiate them that way, and use the proper alloc/init, and release when you are done. This method is much more explicit, and a bit more error prone because if an exception is thrown your release block could get missed, but that is the price you pay for having it that way.

1. If you aren't using alloc/init to get an object, assume it's autoreleased and handle it appropriately. – Abizern Sep 23 '09 at 15:23.

1 That's the fundamental premise of the "retain-release" model, yes. However, if a method returns an object with a +1 retain count (such as if you call +alloc/-init... or -copy or -mutableCopy or something similar) and retain and release it, the object won't be deallocated. That's a "memory leak", and avoiding them is exactly why the OP asked the question.

– Quinn Taylor Sep 23 '09 at 15:47.

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.