| << Chapter < Page | Chapter >> Page > |
This section contains a variety of miscellaneous information.
Financial : Although the Connexionssite makes it possible for you to download a PDF file for this module at no charge, and also makes it possiblefor you to purchase a pre-printed version of the PDF file, you should be aware that some of the HTML elements in this module maynot translate well into PDF.
I also want you to know that, I receive no financial compensation from the Connexions website even if you purchase the PDF version ofthe module.
In the past, unknown individuals have copied my modules from cnx.org, converted them to Kindle books, and placed them for sale onAmazon.com showing me as the author. I neither receive compensation for those sales nor do I know who does receive compensation. If youpurchase such a book, please be aware that it is a copy of a module that is freely available on cnx.org and that it was made andpublished without my prior knowledge.
Affiliation : I am a professor of Computer Information Technology at Austin Community College in Austin, TX.
C. 0 1 2 3 3
No return statement is required
A method with a signature that specifies a void return type does not require a return statement.
However, such a method may contain a return statement, provided that it is terminated immediately with a semicolon (no expression between the word return and the semicolon) .
(Every method whose return type is not void must contain at least one return statement.)
Multiple return statements are allowed
Any method may contain any number of return statements provided that they make sense from a syntax viewpoint, and provided the expression (or lack thereof) between the word return and the semicolon evaluates to the type specified in the method signature (or a type that will be automatically converted to the type specified in the method signature) .
A return statement terminates a method immediately
Whenever the execution stream encounters any return statement, the method is terminated immediately, and control is returned to the method that called thatmethod.
A. Compiler Error
Missing return statement
This program produces the following compiler error under JDK 1.3:
Ap037.java:11: missing return statement
public int doLoop(){ |
Even though this program contains a return statement inside the for loop, it is still necessary to place a return statement at the end of the method to satisfy the compiler. (The one shown in the code is a comment.)
The method named doLoop must return a value of type double . Apparently the compiler assumes that the return statement inside the for loop may never be executed (although that isn't true in this case) .
Both of the return statements must return a value that satisfies the double type requirement given in the method signature.
Notification Switch
Would you like to follow the 'Object-oriented programming (oop) with java' conversation and receive update notifications?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|