何时使用-retainCount?

如果您要查找为什么未释放对象的原因，请使用仪器中的泄漏"工具.如果您试图找出为什么对象被过早释放的原因，请使用Instruments中的僵尸"工具.但不要使用-retainCount.这是一种毫无价值的方法. 修改 请所有人访问 http://bugreport.apple.com ，并要求弃用-retainCount.要求的人越多越好. 修改#2 作为更新，[NSNumber numberWithInt:1]现在具有retainCount的9223372036854775807.如果您的代码期望它为2，则您的代码现在已损坏.I would like to know in what situation did you use -retainCount so far, and eventually the problems that can happen using it.Thanks. 解决方案 You should never use -retainCount, because it never tells you anything useful. The implementation of the Foundation and AppKit/UIKit frameworks is opaque; you don't know what's being retained, why it's being retained, who's retaining it, when it was retained, and so on.For example:You'd think that [NSNumber numberWithInt:1] would have a retainCount of 1. It doesn't. It's 2.You'd think that @"Foo" would have a retainCount of 1. It doesn't. It's 1152921504606846975.You'd think that [NSString stringWithString:@"Foo"] would have a retainCount of 1. It doesn't. Again, it's 1152921504606846975.Basically, since anything can retain an object (and therefore alter its retainCount), and since you don't have the source to most of the code that runs an application, an object's retainCount is meaningless.If you're trying to track down why an object isn't getting deallocated, use the Leaks tool in Instruments. If you're trying to track down why an object was deallocated too soon, use the Zombies tool in Instruments.But don't use -retainCount. It's a truly worthless method.editPlease everyone go to http://bugreport.apple.com and request that -retainCount be deprecated. The more people that ask for it, the better.edit #2As an update,[NSNumber numberWithInt:1] now has a retainCount of 9223372036854775807. If your code was expecting it to be 2, your code has now broken. 这篇关于何时使用-retainCount?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！