Atomic vs nonatomic properties

最新推荐文章于 2024-09-15 19:50:34 发布

WingSu

最新推荐文章于 2024-09-15 19:50:34 发布

阅读量867

点赞数

分类专栏： IOS 文章标签： properties thread setter getter documentation object

IOS 专栏收录该内容

4 篇文章

订阅专栏

本文详细解释了Objective-C中atomic、nonatomic和retain属性的区别，包括它们的功能差异和多线程环境下数据安全性的考虑。

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

Atomic vs nonatomic properties

up vote 356 down vote favorite

189

What do atomic and nonatomic mean in property declarations?

@property(nonatomic, retain) UITextField *userName;

@property(atomic, retain) UITextField *userName;

@property(retain) UITextField *userName;

What is the functional difference between these 3?

edited Feb 7 '11 at 14:35

kiamlaluno
7,775 4 26 37

asked Feb 26 '09 at 2:31

Alex Wayne
28.7k 8 49 94

89% accept rate

Updating the url from Apple's documentation:developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/… – JackDaniels Aug 3 '11 at 19:10

feedback

9 Answers

active oldest votes

up vote 454 down vote accepted

The last two are identical; "atomic" is the default behavior (note that it is not actually a keyword; it is specified only by the absence of nonatomic).

Assuming that you are @synthesizing the method implementations, atomic vs. non-atomic changes the generated code. If you are writing your own setter/getters, atomic/nonatomic/retain/assign/copy are merely advisory.

With "atomic", the synthesized setter/getter will ensure that a whole value is always returned from the getter or set by the setter, regardless of setter activity on any other thread. That is, if thread A is in the middle of the getter while thread B calls the setter, an actual viable value -- an autoreleased object, most likely -- will be returned to the caller in A.

In nonatomic, no such guarantees are made. Thus, nonatomic is considerably faster than "atomic".

What "atomic" does not do is make any guarantees about thread safety. If thread A is calling the getter simultaneously with thread B and C calling the setter with different values, thread A may get any one of the three values returned -- the one prior to any setters being called or either of the values passed into the setters in B and C. Likewise, the object may end up with the value from B or C, no way to tell.

Ensuring data integrity -- one of the primary challenges of multi-threaded programming -- is achieved by other means.