ios developer tiny share-20160914

最新推荐文章于 2020-12-01 15:10:39 发布

原创最新推荐文章于 2020-12-01 15:10:39 发布 · 214 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#ios #objective-c #unsafe_unretained #weak reference #__unsafe_unretained

ios developer tiny share 专栏收录该内容

93 篇文章

订阅专栏

本文介绍了在ARC环境下，对于不支持弱引用的类如NSTextView等，如何使用unsafe_unretained关键字来声明属性和变量。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

今天讲unsafe_unretained以及__unsafe_unretained的关键词使用方法。

Use Unsafe Unretained References for Some Classes
There are a few classes in Cocoa and Cocoa Touch that don’t yet support weak references, which means you can’t declare a weak property or weak local variable to keep track of them. These classes include NSTextView, NSFont and NSColorSpace; for the full list, see Transitioning to ARC Release Notes.

If you need to use a weak reference to one of these classes, you must use an unsafe reference. For a property, this means using the unsafe_unretained attribute:

@property (unsafe_unretained) NSObject *unsafeProperty;

For variables, you need to use __unsafe_unretained:

NSObject * __unsafe_unretained unsafeReference;

An unsafe reference is similar to a weak reference in that it doesn’t keep its related object alive, but it won’t be set to nil if the destination object is deallocated. This means that you’ll be left with a dangling pointer to the memory originally occupied by the now deallocated object, hence the term “unsafe.” Sending a message to a dangling pointer will result in a crash.