forum

Home / DeveloperSection / Forums / I misunderstanding Encapsulation rules in objective c.

Ask Question

I misunderstanding Encapsulation rules in objective c.

Tarun Kumar163920-Aug-2015

I will explain my question from an example.

In .H file//

@interface Employee:NSObject {
 @private NSString *name;
}
 @property(nonatomic,retain) NSString *name;
@end

in .M file//

@implementation {
 @synthesize name; 
}

 

In this scenario when i access the name property within another class , like myEmp.Name = @"John"; it doesn't raise any issue. Does this according to the encapsulation rules or am I misunderstanding?

iphoneiphone ios objective c 
Updated on 21-Aug-2015
Tarun Kumar

Tarun Kumar

Follow

Can you answer this question?

Answer

1 Answers

Anonymous User

Anonymous User

21-Aug-2015

In Objective-C, only an instance method of object can access an instance variable. There is no way for an external object to access the instance variables of an object directly. The @private is only relevant to inheritance.

 

To make the variables accessable there are properties. A property defines a method, and methods on Objective-C are all public. There is no way in Objective-C do define private methods, you can only "hide" them by declaring them somewhere else than the public .h file (e.g. inside the .m file via @interface Employee() which declares an anonymous section).

Liked By