如果您使用的是Leopard (Mac OS X 10.5)或更高版本，则可以使用Instruments应用程序来查找和跟踪内存泄漏。在Xcode中构建程序后，选择使用性能工具> Leaks运行>。

即使你的应用程序没有显示任何泄漏，你可能把对象保存得太久了。在Instruments中，您可以为此使用ObjectAlloc工具。在Instruments文档中选择ObjectAlloc乐器，并通过选择View > detail(它旁边应该有一个复选标记)来显示乐器的详细信息(如果还没有显示的话)。在ObjectAlloc详细信息中的“分配生命周期”下，确保选择“已创建和仍然存在”旁边的单选按钮。

现在，每当您停止记录应用程序时，选择ObjectAlloc工具将在“# Net”列中显示对应用程序中每个仍然活动的对象的引用数。确保不仅要查看自己的类，还要查看NIB文件的顶级对象的类。例如，如果你在屏幕上没有窗口，而你看到一个仍然存在的NSWindow的引用，你可能没有在你的代码中释放它。

黄金法则:如果你分配了，那么你就释放了!

更新:除非你正在使用ARC

功能性更强。

Objective-C是面向对象的语言，但是Cocoa框架是函数式风格的，并且在很多情况下是函数式设计的。

There is separation of mutability. Use immutable classes as primary, and mutable object as secondary. For instance, use NSArray primarily, and use NSMutableArray only when you need. There is pure functions. Not so many, buy many of framework APIs are designed like pure function. Look at functions such as CGRectMake() or CGAffineTransformMake(). Obviously pointer form looks more efficient. However indirect argument with pointers can't offer side-effect-free. Design structures purely as much as possible. Separate even state objects. Use -copy instead of -retain when passing a value to other object. Because shared state can influence mutation to value in other object silently. So can't be side-effect-free. If you have a value from external from object, copy it. So it's also important designing shared state as minimal as possible.

但是也不要害怕使用不纯函数。

There is lazy evaluation. See something like -[UIViewController view] property. The view won't be created when the object is created. It'll be created when caller reading view property at first time. UIImage will not be loaded until it actually being drawn. There are many implementation like this design. This kind of designs are very helpful for resource management, but if you don't know the concept of lazy evaluation, it's not easy to understand behavior of them. There is closure. Use C-blocks as much as possible. This will simplify your life greatly. But read once more about block-memory-management before using it. There is semi-auto GC. NSAutoreleasePool. Use -autorelease primary. Use manual -retain/-release secondary when you really need. (ex: memory optimization, explicit resource deletion)

对于初学者来说，一个很明显的方法是:利用Xcode的自动缩进功能。即使是从其他源复制/粘贴代码，粘贴完代码后，也可以选择整个代码块，右键单击它，然后选择选项重新缩进该代码块中的所有内容。

Xcode会解析这个section并根据括号，循环等缩进它。这比每一行都按空格键或tab键要有效率得多。

打开所有GCC警告，然后关闭那些通常由Apple头文件引起的警告，以减少噪音。

还经常运行叮当静态分析;您可以通过“运行静态分析器”构建设置为所有构建启用它。

编写单元测试，并在每次构建时运行它们。

所有这些评论都很棒，但我真的很惊讶没有人提到谷歌的Objective-C风格指南，这是不久前发布的。我认为他们做得很彻底。