Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Possible Duplicate:
Objective-C properties: atomic vs nonatomic
By default all properties in Objective-C are atomic. If I need nonatomic I have to declare it. But I wonder why should I ever use nonatomic? Even if my applications are not multi threaded, atomic seems like the way to do it. What are the advantages of nonatomic?
A short answer is performance. If you declare properties as
atomic, the synthesized accessors will use locks to ensure that values are fully retrieved and set. If you don’t need this, e.g., your application is single-threaded, you’re incurring a performance penalty for those locks without getting a benefit.