The goal of the @property directive is to make it easy to create and configure properties by automatically generating these accessor methods.
It allows you to specify the behaviour of a public property on a semantic level,
This module surveys the various attributes that let you alter getter and setter behaviour. Some of these attributes determine how properties handle their underlying memory, so this module also serves as a practical introduction to memory management in Objective-C
Property Attributes Indicate Data Accessibility and Storage Considerations
Let's go through the details about these following attributes:
- atomic (default)
- strong=retain (default)
- weak= unsafe_unretained
- assign (default)
- readwrite (defalut)
Where to use atomic in Objective C ?
Why properties are made nonatomic in Objective C?
01.What is atomic in Objective C ?
-Atomic means only one thread access the variable(static type).
-Atomic is thread safe.
-but it is slow in performance
-atomic is default behavior
-Atomic accessors in a non garbage collected environment (i.e. when using retain/release/autorelease) will use a lock to
ensure that another thread doesn't interfere with the correct setting/getting of the value.
-it is not actually a keyword.
@property (retain) NSString *name;
Where to use atomic in Objective C ?
Basic iOS interview Questions And Answers
02. What is non-atomic in Objective C?
-Nonatomic means multiple thread access the variable(dynamic type).
-Nonatomic is thread unsafe.
-but it is fast in performance
-Nonatomic is NOT default behavior,we need to add nonatomic keyword in property attribute.
-it may result in unexpected behavior, when two different process (threads) access the same variable at the same time.
@property (nonatomic, retain) NSString *name;
Suppose there is an atomic string property called "name", and if you call [self setName:@"A"] from thread A,
call [self setName:@"B"] from thread B, and call [self name] from thread C, then all operation on different thread will be performed serially which means if one thread is executing setter or getter, then other threads will wait.
This makes property "name" read/write safe but if another thread D calls [name release] simultaneously then this operation might produce a crash because there is no setter/getter call involved here.
Which means an object is read/write safe (atomic) but not thread safe as another threads can simultaneously send any type of messages to the object.
Developer should ensure thread safety for such objects.
If the property "name" was nonatomic, then all threads in above example - A,B, C and D will execute simultaneously producing any unpredictable result. In case of atomic, Either one of A, B or C will execute first but D can still execute in parallel.
Top 10 Characteristics to become a good developer
03.What is strong (iOS4 = retain ) in Objective C?
It says "keep this in the heap until I don't point to it anymore".
In other words " I am the owner, you cannot dealloc this before I am fine with that same as retain"
You use strong only if you need to retain the object.
By default all instance variables and local variables are strong pointers.
We generally use strong for UIViewControllers
strong is used with ARC and it basically helps you , by not having to worry about the retain count of an object. ARC automatically releases it for you when you are done with it.Using the keyword strong means that you own the object.
@property (strong, nonatomic) ViewController *viewController;
iOS Interview Questions with Answers part3
iOS Interview Questions And Answers Part 9
04. What is weak (iOS4 = unsafe_unretained ) in Objective C?
It says "keep this as long as someone else points to it strongly"
the same thing as assign, no retain or release
A "weak" reference is a reference that you do not retain.
We generally use weak for IBOutlets.This works because the child object only
It needs to exist as long as the parent object does.
A weak reference is a reference that does not protect the referenced object from collection by a garbage collector.
Weak is essentially assign, a unretained property. Except the when the object is deallocated the weak pointer is automatically set to nil
@property (weak, nonatomic) IBOutlet UIButton *myButton;
Imagine our object is a dog, and that the dog wants to run away (be deallocated).
Strong pointers are like a leash on the dog.
As long as you have the leash attached to the dog, the dog will not run away.
If five people attach their leash to one dog, (five strong pointers to one object), then the dog will not run away until all five leashes are detached.
Weak pointers, on the other hand, are like little kids pointing at the dog and saying "Look! A dog!" As long as the dog is still on the leash, the little kids can still see the dog, and they'll still point to it.
As soon as all the leashes are detached, though, the dog runs away no matter how many little kids are pointing to it.
As soon as the last strong pointer (leash) no longer points to an object, the object will be deallocated, and all weak pointers will be zeroed out.
When we use weak?
The only time you would want to use weak, is if you wanted to avoid retain cycles (e.g. the parent retains the child and the child retains the parent so neither is ever released).
iOS Interview Questions with Answers part 2
iOS Interview Questions and Answers part 1
05.What is retain = strong in Objective C?
It is retained, old value is released and it is assigned.
retain specifies the new value should be sent
retain on assignment and the old value sent -release.
retain is the same as strong.
apple says if you write retain it will auto converted/work like strong only.
methods like "alloc" include an implicit "retain".
@property (nonatomic, retain) NSString *name;
How to animate a view or image along a curved path.
iOS Interview Questions And Answers Part 10
iOS Interview Questions And Answers Part12
06.What is assign in Objective C?
assign is the default and simply performs a variable assignment.
assign is a property attribute that tells the compiler how to synthesize the property's setter implementation.
I would use assign for C primitive properties and weak for weak references to Objective-C objects.
@property (nonatomic, assign) NSString *address;
What are the differences between Cocoa and Cocoa Touch?
07.What is unsafe_unretained in Objective C?
-unsafe_unretained is an ownership qualifier that tells ARC how to insert retain/release calls
-unsafe_unretained is the ARC version of assign.
@property (nonatomic, unsafe_unretained) NSString *nickName;
List of design patterns adapted by Cocoa.
08.What is copy in Objective C?
copy is required when the object is mutable.
copy specifies the new value should be sent .
copy on assignment and the old value sent release.
copy is like retain returns an object which you must explicitly release (e.g., in dealloc) in non-garbage collected environments.
if you use copy then you still need to release that in dealloc.
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.
@property (nonatomic, copy) NSArray *myArray;
What is MVC in iPhone?
iOS Interview Questions And Answers Part13
09.What is readonly in Objective C?
Declaring your property as readonly you tell compiler to not generate setter method automatically.
Indicates that the property is read-only.If you specify readonly, only a getter method is required in the @implementation block.
If you use the @synthesize directive in the @implementation block, only the getter method is synthesized.
Moreover, if you attempt to assign a value using the dot syntax,
you get a compiler error.
@property (nonatomic, readonly) NSString *name;
Top iOS Interview Questions And Answers for Beginners
What is the use of plist ?
What is .ipa in iOS ?
10. What is readwrite in Objective C ?
setter and getter generated by the compiler.
It Indicates that the property should be treated as read/write.
This attribute is the default.
Both a getter and setter method are required in the @implementation block. If you use the @synthesize directive in the implementation
block, the getter and setter methods are synthesized.
@property (nonatomic, readwrite) NSString *name;
What is .xib in iOS ?
Core Data Interview Questions and Answers