假期如何学java_假期回国自学java，弱弱从头开始

随机写点看到的技术知识点总结，留着自己忘了的时候看一看，学一学.也把别人的答案记录在案。

Constructor and Setter

If there are no setters, it basically means that you want to initialize the class with data, but don’t want it to be changed.  For me, when developing, I basically think about what the class does and whether all the data, some of it, or none of it needs to be changed.

Take for instance the following Person class

We know that a person could have their first name, last name, and definitely their age changed throughout the course of their life.  As such, in the program, we provide the class with the ability to change any of the fields so that we could come back at a later time and change it.  When we create a new Person, we want that person to have a First Name, Last Name, and Age so we make a constructor for it.

But, sometimes, we want to make a class where we can initialize data in the fields, but we don’t want that data to change at all.  Take the following simple, yet hopefully fun, example:

In this example, the Person class only has one field: favorite language.  Now, when we initialize the class, the favorite (programming) language is set for that person; however, that person really just loves that language and has vowed to never change it in his/her lifetime.  As such, we can get the person’s favorite language, but we cannot change it.

These are very simple examples. But, to answer your question

`How do you tell if you should use setters or not and if a constructor should be written`

1) You use setters if you want any of the data in that class to be changed.  You can have a setter for every field, for some of them, or for none of them at all because you feel that the fields don’t need to be changed based on the goal of that particular class.

2) Whenever you want to initialize fields with data when the class is initialized, you would use constructors.  If the class has no fields to initialize, you don’t need to provide a constructor since there is an implicit one provided for you.

You can see that there are no fields that this class has to initialize.  As such, you don’t need to provide a constructor.  When you initialize the class:

Person me = new Person();

there is a hidden constructor, a `default` constructor that is automatically generated for you.

You can write one yourself, all you would essentially do is type this for the above class:

publicPerson(){

}

But we want to make things easier for ourselves so we don’t even bother typing it most of the time.

However, there will be situations where we have fields in our class, but yet we want to initialize them with default values rather than with data provided by the constructor.  This is where you would manually make an empty constructor to initialize the fields:

~~ Summary ~~

Constructors:

1) If you have fields that need to have data initialized with values provided by you, make a constructor that has the data to initialize the fields.

2) If there is nothing to initialize, you don’t have to provide a constructor since the compiler generates one for you, although you can still provide your own.

3) If you have fields that you want to initialize, but yet you don’t want them to have the values initialized by data coming in to the constructor, just make a constructor with no parameters and set it there.

Setters:

1) If you want that field to change at a later time, provide a setter for it.

2) You don’t have to provide setters for all fields in the class.  Remember: if you believe that the data will change in the future, provide a setter for it.  If you don’t think it will/needs to be changed in the future, you can omit the setter for it.  (This could be a repeat of (1) lol).