ios学习之内存管理

https://developer.apple.com/library/ios/documentation/cocoa/Conceptual/MemoryMgmt/Articles/mmRules.html#//apple_ref/doc/uid/20000994-BAJHFBGH

对对象的所有权的管理是ios对内存管理的核心，这个和C＋＋很不同，C＋＋更加底层，是直接对内存的操作，ios封装的程度更高面向对象程度也更高一些，再强调一下，分析所有权是分析内存的关键。

下面四条规则是对所有权的最基本的定义，就像宪法一样是一切的基础，但是对于像某些不严格按照法理去制定其他的规则的国家，这些都是废话。

The memory management model is based on object ownership. Any object may have one or more owners. As long as an object has at least one owner, it continues to exist. If an object has no owners, the runtime system destroys it automatically. To make sure it is clear when you own an object and when you do not, Cocoa sets the following policy:

• You own any object you create

  You create an object using a method whose name begins with “alloc”, “new”, “copy”, or “mutableCopy” (for example, alloc, newObject, or mutableCopy).

• You can take ownership of an object using retain

  A received object is normally guaranteed to remain valid within the method it was received in, and that method may also safely return the object to its invoker. You use retain in two situations: (1) In the implementation of an accessor method or an init method, to take ownership of an object you want to store as a property value; and (2) To prevent an object from being invalidated as a side-effect of some other operation (as explained in “Avoid Causing Deallocation of Objects You’re Using”).

• When you no longer need it, you must relinquish ownership of an object you own

  You relinquish ownership of an object by sending it a release message or an autorelease message. In Cocoa terminology, relinquishing ownership of an object is therefore typically referred to as “releasing” an object.

• You must not relinquish ownership of an object you do not own

  This is just corollary of the previous policy rules, stated explicitly.

Use autorelease to Send a Deferred release

下面的三个例子很耐看，值得去推敲。

You use autorelease when you need to send a deferred release message—typically when returning an object from a method. For example, you could implement the fullName method like this:

- (NSString *)fullName {

NSString *string = [[[NSString alloc] initWithFormat:@"%@ %@",

self.firstName, self.lastName] autorelease];

return string;

}

You own the string returned by alloc. To abide by the memory management rules, you must relinquish ownership of the string before you lose the reference to it. If you use release, however, the string will be deallocated before it is returned (and the method would return an invalid object). Using autorelease, you signify that you want to relinquish ownership, but you allow the caller of the method to use the returned string before it is deallocated.

You could also implement the fullName method like this:

- (NSString *)fullName {

NSString *string = [NSString stringWithFormat:@"%@ %@",

self.firstName, self.lastName];

return string;

}

Following the basic rules, you don’t own the string returned by stringWithFormat:, so you can safely return the string from the method.

By way of contrast, the following implementation is wrong:

- (NSString *)fullName {

NSString *string = [[NSString alloc] initWithFormat:@"%@ %@",

self.firstName, self.lastName];

return string;

}

According to the naming convention, there is nothing to denote that the caller of the fullName method owns the returned string. The caller therefore has no reason to release the returned string, and it will thus be leaked.