Objective-C declared @property attributes (nonatomic, copy, strong, weak)

by

Nonatomic

Nonatomic will not generate threadsafe routines thru @synthesize accessors. atomic will generate threadsafe accessors so atomic variables are threadsafe (can be accessed from multiple threads without botching of data)

Copy

copy is required when the object is mutable. Use this if you need the value of the object as it is at this moment, and you don’t want that value to reflect any changes made by other owners of the object. You will need to release the object when you are finished with it because you are retaining the copy.

Assign

Assign is somewhat the opposite to copy. When calling the getter of an assign property, it returns a reference to the actual data. Typically you use this attribute when you have a property of primitive type (float, int, BOOL…)

Retain

retain is required when the attribute is a pointer to a reference counted object that was allocated on the heap. Allocation should look something like:

NSObject* obj = [[NSObject alloc] init]; // ref counted var

The setter generated by @synthesize will add a reference count to the object when it is copied so the underlying object is not autodestroyed if the original copy goes out of scope.

You will need to release the object when you are finished with it. @propertys using retain will increase the reference count and occupy memory in the autorelease pool.

Strong

strong is a replacement for the retain attribute, as part of Objective-C Automated Reference Counting (ARC). In non-ARC code it’s just a synonym for retain.

This is a good website to learn about strong and weak for iOS 5.
http://www.raywenderlich.com/5677/beginning-arc-in-ios-5-part-1

Weak

weak is similar to strong except that it won’t increase the reference count by 1. It does not become an owner of that object but just holds a reference to it. If the object’s reference count drops to 0, even though you may still be pointing to it here, it will be deallocated from memory.

The above link contain both Good information regarding Weak and Strong.

More Related Contents:

  1. How can I disable ARC for a single file in a project?
  2. How does the new automatic reference counting mechanism work?
  3. Why is @autoreleasepool still needed with ARC?
  4. How do I avoid capturing self in blocks when implementing an API?
  5. How do I implement an Objective-C singleton that is compatible with ARC?
  6. Do declared properties require a corresponding instance variable?
  7. Does ARC support dispatch queues?
  8. Disable Automatic Reference Counting for Some Files
  9. Handling Pointer-to-Pointer Ownership Issues in ARC
  10. self.variable and variable difference [duplicate]
  11. ARC and bridged cast
  12. Some questions about Automatic Reference Counting in iOS5 SDK
  13. Should I refer to self.property in the init method with ARC?
  14. Weak NSString variable is not nil after setting the only strong reference to nil
  15. capturing self strongly in this block is likely to lead to a retain cycle
  16. In which situations do we need to write the __autoreleasing ownership qualifier under ARC?
  17. NSArray of weak references (__unsafe_unretained) to objects under ARC
  18. AVAudioPlayer not playing any sound
  19. NSString to CFStringRef and CFStringRef to NSString in ARC?
  20. Get property name as a string
  21. ARC – The meaning of __unsafe_unretained?
  22. With ARC, what’s better: alloc or autorelease initializers?
  23. Instance variables declared in ObjC implementation file
  24. Retain Cycle in ARC
  25. When converting a project to use ARC what does “switch case is in protected scope” mean?
  26. How to enable ARC for a single file
  27. Zeroing Weak References in ARC
  28. Why does ARC retain method arguments?
  29. Why can’t I release an object anymore? [duplicate]
  30. fake va_list in ARC

Leave a Comment