getter

Possible Duplicate: Why use getters and setters? I have read books on Java , saying that it is good to create setters and getters for variables such as x and y . For example: public int getX(){ return x; } public void setX(int x){ this.x = x; } But what is the difference from that and ...(shape.x)... // basically getX() and shape.x = 90; // basically setX() If setters and getters are better, could you explain to me what practical problems would arise? mprabhat Multiple reasons: If you allow field access like shape.x = 90 then you cannot add any logic in future to validate the data. say if x

EDIT Oct 2016 : Please note this question was asked in 2012. Every month or so someone adds a new answer or comment that refutes an answer, but doesn't really make sense to do so as the question is probably out of date (remember, it was for Gnome Javascript to write gnome-shell extensions, not browser stuff, which is quite specific). Following my previous question on how to do subclassing in Javascript, I'm making a subclass of a superclass like so: function inherits(Child,Parent) { var Tmp = function {}; Tmp.prototype = Parent.prototype; Child.prototype = new Tmp(); Child.prototype

I have searched many questions on ObjC accessors and synthesized accessors to no avail. This question is more of a "help me settle an issue" question; I don't expect one answer, but I'm rather looking for experts to weigh in on the argument. In a Cocoa Touch class, I would write some code like this (where soundEffects is a synthesized NSArray property): id foo = [self.soundEffects objectAtIndex:1]; A colleague asked me to explain why the above is any better than this line: id foo = [soundEffects objectAtIndex:1]; Well, functionally, it's no different. My arguments for the former are as follows

Normally we use @interface interface_name : parent_class <delegates> { ...... } @end method in .h file and in .m file we synthesis the properties of variables declared in .h file. But in some code, this @interface.....@end method is kept in the .m file also. What does it mean? What is the difference between them? Also give some words about getters and setters for the interface file that is defined in .m file... Thanks in Advance Benedict Cohen It's common to put an additional @interface that defines a category containing private methods: Person.h: @interface Person { NSString *_name; }