getter

If you have a class with some plain get/set properties, is there any reason to use the getters within the class methods, or should you just use the private member variables? I think there could be more of an argument over setters (validation logic?), but I'm wondering just about getters. For example (in Java) - is there any reason to use option 2?: public class Something { private int messageId; public int getMessageId() { return this.messageId; } public void setMessage(int messageId) { this.messageId = messageId; } public void doSomething() { // Option 1: doSomethingWithMessageId(messageId);

I have a a couple of variables that i define in C# by: public String firstName { get; set; } public String lastName { get; set; } public String organization { get; set; } What i want is to add validation to these methods when you try to set a value. Lets say your going to set a value for firstName, the i should pass thrue a regexp to actuelly be set, otherwise an exception should be thrown. Is this possible to build with this "short syntax" or should I go for standard (like in JAVA) getters and setters and in there validate the data? jason If you want to validate when the property is set, you

What is the best practice for a C++ getter method which is supposed to return a non trivial type, but a member which is of type class, or struct. Return by value, such as: MyType MyClass::getMyType() { return mMyType; } Return by const reference: const MyType& MyClass::getMyType() { return mMyType; } Return by address: MyType* MyClass::getMyType() { return &mMyType; } where class MyType { /* ... */ }; class MyClass { private: MyType mMyType; } I specifically worry about the following usages of this method. Can you please elaborate in details how this might affect copying the object, and the

I have a strange habit it seems... according to my co-worker at least. We've been working on a small project together. The way I wrote the classes is (simplified example): [Serializable()] public class Foo { public Foo() { } private Bar _bar; public Bar Bar { get { if (_bar == null) _bar = new Bar(); return _bar; } set { _bar = value; } } } So, basically, I only initialize any field when a getter is called and the field is still null. I figured this would reduce overload by not initializing any properties that aren't used anywhere. ETA: The reason I did this is that my class has several

I do not really understand how getter and setter work althougth it is a basic concept. I have the following code, how is the attribute id sent to Managed Bean? Is it captured by getter method? My facelet <p:inputText id="id" value="#{bean.id}"> My managed bean private String id; public void setId(String id) { this.id = id; } public String getId() { return id; } Luiggi Mendoza The call of getter and setter methods by #{} expressions is not part of JSF but Expression Language (most known as EL). JSF takes advantage of EL to bind the data of the HTML components to the fields of a bean through

Let's have an object created in a getter like this : public class Class1 { public string Id { get; set; } public string Oz { get; set; } public string Poznamka { get; set; } public Object object { get { // maybe some more code return new Object { Id = Id, poznamla = Poznamka, Oz = OZ }; } } } Or should I rather create a Method that will create and return the object ? Sergey Teplyakov Properties look like fields but they are methods. This has been known to cause a phenomenal amount of confusion. When a programmer sees code that appears to be accessing a field, there are many assumptions that