Using Properties in Objective-C Tutorial 边看边记

Using Properties in Objective-C Tutorial

This approach definitely works, but requires you to think carefully about what’s going on with memory each time you set these variables. So let’s see if there’s an easier way!

第一次看到prtoperty是以这种形式引出来的，一般都是，嫌写getter setter方法麻烦。

When you have an instance variable such as _sushiTypes, you often want another class to be able to access it. But it’s generally bad practice to allow classes to directly access instance variables, because it makes your code brittle.

哎，我写的程序一般都是brittle的。

又得出去一趟，回来继续看。

周六早上开始看的，现在是周一晚上，好歹是看完了。文章还是不错的，以下的内容，我也从来没有再中文的文章中，看到过，很精辟

I’ll list the rules out first, and then we’ll have a discussion of each one.

1. Always make a property for every instance variable.
2. If it’s a class, mark it with the retain attribute. Otherwise, mark it with the assign attribute.
3. Whenever creating a variable, use the alloc/init/autorelease idiom.
4. Whenever setting a variable, always use “self.xxx = yyy” (in other words, use the property).
5. For each of your instance variables, call “self.xxx = nil” in dealloc. If it’s an outlet or something you created in viewDidLoad, do the same in viewDidUnload.

Ok, now onto the discussion!

For rule #1: By making an instance variable for each property, you can let the compiler write the memory management code for you. The drawback is it doesn’t keep the private data of your class well encapsulated so can lead to more connected code if you are not careful.

For rule #2: By retaining variables whenever they are set, you can make sure that you can access your instance variables at any time.

For rule #3: When you create a variable, you want to use the alloc/init/autorelease idiom (like you can see creating the NSArray with the sushiTypes earlier). This way, the memory will be freed up for you automatically later on. If you need to keep the variable around long-term, you should assign it to a property, put it in an array, or the like to increment the reference count.

For rule #4: By using the self.xxx syntax (i.e. using the property) whenever you set a variable, you’ll go through the properties and hence make sure to release the old variable/retain the new variable. Note some programmers worry about using getters/setters/properties in initializers and dealloc, but I don’t think it’s something to worry about if you wrote & understand the code.

For rule #5: Calling “self.xxx = nil” will go through your properties and decrement the reference count. Don’t forget about viewDidUnload!

继续修炼，屌丝总有出头日