对于 iOS 开发人员，委托几乎无处不在.
For iOS developers, delegates are used almost everywhere.
对于这样的委托，我们似乎需要使用分配"而不是保留
And seems like that we need to use "assign" instead of retain for a delegate like this
@property(assign) id delegate;
原因是为了避免循环循环问题 为什么 Objective-C 委托通常被赋予属性 assign 而不是保留?
The reason is to avoid the circular loop issue Why are Objective-C delegates usually given the property assign instead of retain?
我看了很多代码，他们仍然使用保留".所以这里的问题是，如果我们对委托使用保留，我们还会遇到循环循环问题吗?
I saw a lot of code and they still used "retain". So the question here is will we still get the circular loop issue if we use retain for a delegate?
谢谢
文档 说:
保留一个对象会创建一个强引用，并且一个对象在其所有强引用都被释放之前不能被释放.如果两个对象相互保留，则两个对象都不会被释放，因为它们之间的连接不会被破坏
Retaining an object creates a strong reference, and an object cannot be deallocated until all of its strong references are released. If two objects retain each other, neither object ever gets deallocated because the connection between them cannot be broken
作为一个例子，让我们考虑一个实现 UITableViewDelegate 协议的 UITableViewController.UITableView 由它的视图控制器保留，尽管 UITableView 不保留它的委托.
As an example, let's consider a UITableViewController that implements UITableViewDelegate protocol. UITableView is retained by it's view controller, although the UITableView does not retain it's delegate.
正如上面文档中所说，UITableViewController 只有在其所有强引用都被释放时才会完成其释放.由于以 UItableViewController 作为委托的 UITableView 不保留它，所以当 UItableViewController 的所有者对其调用 release 时，保留计数将归零并调用 dealloc 方法.
As said on the document above, UITableViewController will only complete its deallocation when all its strong references get released. Since the UITableView that has the UItableViewController as a delegate doesn't retain it, when the owner of UItableViewController calls release on it, the retain count will go to zero and the dealloc method will get called.
现在假设 UITableView 保留了它的委托.UITableViewController 的保留计数至少为 +2.一个是它的所有者，另一个是 UITableView.当 UITableViewController 的所有者对其调用 release 时，保留计数将变为 +1，而不是预期的为零，因此在保留计数达到零之前不会调用 dealloc 方法.为了达到零，UITableViewController 需要释放它的 UITableView，然后释放它的委托(UITableViewController).因为 UITableViewController 只会在释放它的视图(UITableView)时释放这个时刻永远不会发生，因为保留计数不会低于 +1.
Now imagine that UITableView retains its delegate. UITableViewController will have a retain count of at least +2. One with it's owner and another with UITableView. When UITableViewController's owner calls release on it, the retain count will go to +1, and not to zero as it was expected, and so the dealloc method won't get called until the retain count reaches zero. To reach zero, UITableViewController would need to release its UITableView that would then release its delegate (UITableViewController). Because the UITableViewController will only disposes its view (UITableView) when deallocing this moment would never happen because the retain count won't go bellow +1.
(让我们不要考虑内存警告和任何其他可能的情况......我刚刚看到 ViewController/View 不是这个示例的最佳选择，但我已经写了太多了.:))
(let's not take in consideration memory warnings and any other possible case...I just saw that ViewController/View is not the best option for this example, but I've written too much already. :))
这有意义吗?
这篇关于属性“分配"；和“保留"代表的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！