Welcome to the Java Programming Forums
The professional, friendly Java community. 21,500 members and growing!
The Java Programming Forums are a community of Java programmers from all around the World. Our members have a wide range of skills and they all have one thing in common: A passion to learn and code Java. We invite beginner Java programmers right through to Java professionals to post here and share your knowledge. Become a part of the community, help others, expand your knowledge of Java and enjoy talking with like minded people. Registration is quick and best of all free. We look forward to meeting you.
>> REGISTER NOW TO START POSTING
Members have full access to the forums. Advertisements are removed for registered users.
LinkBack URL
About LinkBacks
Why getMethod, but not set method
Very often I see in Java code a constructor been used instead of void setColor() method for example.
Why would somebody do this?
So why doing this:
public class Dog { String color; public Dog(String color) { this.color = color; } }
Instead of:
public class Dog { String color; public void setColor(String color) { this.color = color; } }
Re: Why getMethod, but not set method
The object itself may change the variable after initialization, but it would undesirable to change the variable from outside.
jenniferruurs (October 7th, 2019)
Reply With Quote