Answer:
Yes. It is OK to have a return statement at the end of a method, even though it is not needed.
In this example the return does not return a value to the caller, which agrees with the void
return value for the method.
Yes. It is OK to have a return statement at the end of a method, even though it is not needed.
In this example the return does not return a value to the caller, which agrees with the void
return value for the method.
The Java interpreter starts a program by looking
for a static main() method
inside of the HelloTester.class file.
Since the method is static
the interpreter can run it
without first constructing an object.
It is convenient to have a separate class that
serves no other purpose than to contain the main() method.
This testing class is used to start things running.
Usually main() constructs objects
of various classes and calls their methods.
These objects do the real work of the program.
The source file for the program is named HelloTester.java.
When you compile the file, the compiler outputs
two separate files of bytecodes, one for each class:
C:\chap30>javac HelloTester.java
C:\chap30>dir
11/13/98 10:07p 257 HelloTester.java
11/13/98 10:40p 476 HelloObject.class
11/13/98 10:40p 373 HelloTester.class
3 File(s) 1,106 bytes
To run the program, type:
java HelloTester
The Java interpreter finds the main() method in
the HelloTester class and starts it running.
Of course, with an IDE like BlueJ you run the program directly from the visual interface. Class files are still created, however, and can be found somewhere in the directories created for the project.
When the Java interpreter needs the definition
HelloObject,
where will it be found?