财产“转让"和“保留"代表 [英] property "assign" and "retain" for delegate

查看:16
本文介绍了财产“转让"和“保留"代表的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

对于 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 而不是retain?

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. :))

有意义吗?

这篇关于财产“转让"和“保留"代表的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆