Ans :
Strong
A strong property means that you want to “own” the object. Only when you set the property to nil will the object be destroyed. Unless one or more objects also have a strong reference to the object. This is the one you will use in most cases.
- Creates ownership between property and assigned value.
- This is default for object property in ARC so it does not let you worrying about reference count and release the reference automatically.
- It is replacement for retain. We use if and only if we need to use as retain.
- Retain count will be incremented.
- Creates non-ownerships between property and assigned value.
- Strong is used on parent object and weak is used on child object when parent is released then child object reference is also set to nil
- It helps to prevents retain cycles.
- It doesn’t protect the referenced object when collection by garbage collector.
- Weak is essentially assigned, un-retain property.
- Retain count will not be incremented.
Weak
Weak property means you don’t want to have control over the objects lifecycle. The object only lives on while another objects has a strong reference to it. If there are no strong references to the object then it will be destroyed.
Weak reference is useful to avoid situation like retain cycle. Retain cycle occurs when two or more objects have strong reference to each other. This two object will never be freed in memory due to strong reference. So to avoid weak reference, One object has a strong ownership reference to another object, and another object should be have a weak reference to first object.
Strong references should be used when a parent object is referencing a child object and never the other way around. That is, a child class should not have a strong reference to the parent class.
Weak references should be used to avoid retain cycles and an object has the possibility to become nil at any point of it’s lifetime.
Good read : Click here
No comments:
Post a Comment
Thanks