Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
Java
Please comment on this class hierarchy design
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Jason, post: 530628"] I've been known to use both, but not interchangeably. An abstract class is very useful for things that you don't want to instantiate, for example a factory class that has a single method who's job it is to spit up an instance of several related classes based on some criterion. I would be careful of the blanket statement that an interface is "better" ... It is certainly better for some things and in some implementations, most quite probably, but there are cases and situations where an abstract class is not only viable, it's also an exceptional resolution. Just my 2 krupplenicks on the subject. [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
Java
Please comment on this class hierarchy design
Top