File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Junior/Associate Certification (SCJA,OCAJ 5/6/8) and the fly likes SCJA Question About Ancestor and Sub Classes Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Certification » Junior/Associate Certification (SCJA,OCAJ 5/6/8)
Bookmark "SCJA Question About Ancestor and Sub Classes" Watch "SCJA Question About Ancestor and Sub Classes" New topic

SCJA Question About Ancestor and Sub Classes

Oscar Hansen

Joined: Jul 09, 2008
Posts: 10
I am reading SCJA book by Cameron McKenzie and on page 166, I did not understand the answer to a question. Can someone explain me:

Sub classes:
- Should not be used as a method parameters when an ancestor class will suffice.

Thanks in advance!
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper

Joined: Aug 26, 2006
Posts: 4968

The basic idea is that you always want to use the most general component whenever possible.

So, if I have a method, and all it does is print out the toString() method, I shouldn't force the argument to be a String, when I could just make the argument an Object. After all, every instance of an Object has a toString() method.

The more general, or abstract an argument is, the more flexible the method becomes. It makes your code more flexible and pluggable. That's the general idea.
I agree. Here's the link:
subject: SCJA Question About Ancestor and Sub Classes
It's not a secret anymore!