| << Chapter < Page | Chapter >> Page > |
I recommend that you open another copy of this document in a separate browser window and use the following links to easilyfind and view the listings while you are reading about them.
This section contains a variety of miscellaneous information.
Financial : Although the Connexions site makes it possible for you to download aPDF file for this module at no charge, and also makes it possible for you to purchase a pre-printed version of the PDF file, youshould be aware that some of the HTML elements in this module may not 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. 38.4845100064749612.566370614359172 Use static methods sparingly
Good object-oriented design dictates that static methods be used sparingly, and only in those situations where they are appropriate. As youmight guess, not all authors will agree on the issue of appropriateness in all cases.
Is this an appropriate use of a static method?
However, I believe that most authors will agree that this program illustrates an appropriate use of a static method.
No persistence requirement
This static method computes and returns a result on a non-persistent basis. That is to say, there is no attempt by the static method to save any historical information from one call of the method to thenext. (Of course, the method that calls the static method can save whatever it chooses to save.)
Avoiding wasted computer resources
In situations such as this, it would often be a waste of computer resources to require a program to instantiate an object and call an instance method onthat object just to be able to delegate a non-persistent computation to that method. (This is just about as close to a global method as you can get in Java.)
Notification Switch
Would you like to follow the 'Object-oriented programming (oop) with java' conversation and receive update notifications?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|