A deep understanding of the meaning of Java initialization-general Linux technology-Linux programming and kernel information. The following is a detailed description. We can think that each class has a method named Initialize (). This name implies that it must be called before use. Unfortunately, in this case, you have to remember to call this method. java class library designers can use a special method called constructor to ensure that every object can be initialized. if there is a constructor in the class, java will automatically call the constructor when the object is just created and the user is too late to obtain it, so that initialization is guaranteed.
I don't know how much the difference between the original author's description and the translator's understanding is. Combined with the entire chapter, I didn't find two key words "" and "". At least the author and the translator did not really explain what the JVM did during initialization, or did not understand the JVM initialization details. Otherwise, the two methods are clearly available, but why do you think there is a "Initialize ()" method that actually does not exist?
Where are the "and" methods? These two methods actually exist and you cannot find them. This may make some masters confused. Coupled with some bugs in jdk implementation, if you do not have a deep understanding, it is really hard to understand.
Now there is a strange phenomenon in the scientific system, so a huge system was initially built on the basis of a hypothesis: Suppose 1 is correct, then 2 is derived, and then continue to export 10000000000. Unfortunately, too many people do not care about systems like 2-00000000000, which are based on the assumption that 1 is correct. I will not use the assumption that "we can think like this". I want to prove that "and" "methods actually exist:
CODE: package debug;
Public class MyTest {
Static int I = 100/0;
Public static void main (String [] args ){
Ssytem. out. println ("Hello, World! ");
}
} |
