I was wondering how you guys decide when to use abstract or interface class during the application development since they both provide similar functionalities with slightly difference. I appreciate any helps. Thanks.
2
-
possible duplicate of interface vs abstract classVolkerK– VolkerK2010-09-06 19:15:34 +00:00Commented Sep 6, 2010 at 19:15
-
possible duplicate of PHP: What is the difference between an interface and abstract class?Gordon– Gordon2010-09-15 22:37:48 +00:00Commented Sep 15, 2010 at 22:37
Add a comment
|
6 Answers
Use abstraction if you have default methods (with accompanying code) for inheritors. Use interfaces if you just need to make sure that classes inheriting from this parent should implement all methods defined. Word of caution: use abstract classes and interfaces only if you intend to enforce structure and organization (usually with a team). There's a performance overhead.
Comments
I use abstract classes when I want the inheriting classes to inherit some functionality, and interfaces when I want to set some minimum structural criteria for a group of classes.
One thing to remember is that any given class can "inherit" (technically implement) many interfaces but only one sub-class (be that abstract or not).
Comments
when i'm developing and trying to decide whether to use an interface or an abstract class i usually think about whether classes that will inherit will contain only the same structure (methods, properties etc) but different implementations.
if the implementation of the methods will be different, but i want to ensure sameness from a structural standpoint i use an interface. if the structure and implementation are the same i tend to use abstract classes.
2 Comments
RN Kushwaha
It does not make clear why
if the structure and implementation are the same i tend to use abstract classes you use abstract class if same structure and implementation needed?
nathan gonzalez
@RNKushwaha, I mean that if i want to share an identical implementation of a method/property between multiple inheriting classes, i would create an abstract class so that the implementation could live in the abstract class. Interfaces don't allow any implementation. Does that make more sense?
Languages like PHP support multiple interface implementation but not multiple class inheritance, and this is often part of the decision -- will your class support multiple behaviors (interfaces) or will it act as one type of thing (base class)?
There is also the question of how the base functionality is implemented. If you are using an approach like the template method pattern where you have common implementation code for all derived classes, you will want to use an abstract base class.
Comments
Here is good article explaining concept of interface and why to use it and how to declare abstract classes in PHP.Though it does not differentiate when to use both concepts.
Understanding and Applying (Interfaces) Polymorphism in PHP
Comments
when you bound for certain functionality is required--use interface.but if you want some optional functionality --use abstract class . for example if isi(indian standard institute) makes a standards for computer monitor with functionality(it should have)--Display,power button,contrast setter. if all 3 functionality is compulsory then use interface, which bound monitor manufacturer company to implement all 3 functionality. if any is optional then use abstract class.
Comments
