This question already has answers here: Why use getters and setters/accessors? (41 answers) Closed 6 years ago. I’m currently working on a simple game in Java with several different modes. I’ve extended a main Game class to put the main logic within the other classes. Despite this, the main game class is still pretty hefty. … Read more
By “generate”, I mean auto-generation of the code necessary for a particular selected (set of) variable(s). But any more explicit explication or comment on good practice is welcome. 16 Answers 16
Let’s say I specify an outputText component like this: <h:outputText value=”#{ManagedBean.someProperty}”/> If I print a log message when the getter for someProperty is called and load the page, it is trivial to notice that the getter is being called more than once per request (twice or three times is what happened in my case): DEBUG … Read more
I am creating all of the elements in my android project dynamically. I am trying to get the width and height of a button so that I can rotate that button around. I am just trying to learn how to work with the android language. However, it returns 0. I did some research and I … Read more
What’s the advantage of using getters and setters – that only get and set – instead of simply using public fields for those variables? If getters and setters are ever doing more than just the simple get/set, I can figure this one out very quickly, but I’m not 100% clear on how: public String foo; … Read more
How do you give a C# auto-property an initial value? I either use the constructor, or revert to the old syntax. Using the Constructor: class Person { public Person() { Name = “Initial Name”; } public string Name { get; set; } } Using normal property syntax (with an initial value) private string name = … Read more
They don’t allow you to specify encapsulating behavior. What they do is allow you to specify that this is a Property in the public interface of your class, as opposed to a field. The difference here is that in Java, getters and setters are simply methods that follow a certain convention (getXXX, setXXX). In C#, … Read more
There are actually many good reasons to consider using accessors rather than directly exposing fields of a class – beyond just the argument of encapsulation and making future changes easier. Here are the some of the reasons I am aware of: Encapsulation of behavior associated with getting or setting the property – this allows additional functionality (like validation) … Read more