Is return autorelease a bug in objective c?

In your second example, the anonymous object you're returning will not be released as soon as the execution leaves the scope of makeBar but on the next iteration of the run loop. This will give you the opportunity to retain it in whatever method has called makeBar So your final example is ok since the retain count will not drop below 0 Are you having trouble with it?

In your second example, the anonymous object you're returning will not be released as soon as the execution leaves the scope of makeBar but on the next iteration of the run loop. This will give you the opportunity to retain it in whatever method has called makeBar So your final example is ok since the retain count will not drop below 0. Are you having trouble with it?

1 To be more specific, it will be released when the autorelease pool that it was added to is drained/released. This is typically at the end of a run loop, but not always. – dreamlax Feb 17 '10 at 18:57 No problems, I've just been scanning my code for potential memory issues and saw that pattern from sample code I had copied and wasn't sure if it was a bug or not.

– esilver Feb 17 '10 at 22:30.

(Bar*) makeBar { return Bar alloc init autorelease; } The 2nd case is the preferred way to return an Objective-C object. Except +alloc, -copy... and -create..., the method should retain no ownership of the returning object, i.e. The (change of) retain count should be 0.

However, Bar alloc init makes the object to have retainCount of +1, to one should release it before return. But -release will immediate deallocate the object, making the method useless. That's why -autorelease is used — it is a delayed -release, i.e.

The object will be released eventually, but not now, so other parts of code can still interact with it, yet the retain count can still be balanced to 0. Bar *b = self makeBar retain; You should not retain it unless you want to be a long-term owner of the object b.

The 2nd case is the preferred way to return an Objective-C object. Except +alloc, -copy... and -create..., the method should retain no ownership of the returning object, i.e. The (change of) retain count should be 0.

However, Bar alloc init makes the object to have retainCount of +1, to one should release it before return. But -release will immediate deallocate the object, making the method useless. That's why -autorelease is used — it is a delayed -release, i.e.

The object will be released eventually, but not now, so other parts of code can still interact with it, yet the retain count can still be balanced to 0. You should not retain it unless you want to be a long-term owner of the object b.

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.

Related Questions