What decision will you make Abstract Class or Interface Class

Question

0.00/5 (No votes)

See more:

Which should i need to use ...My requirement gets change in Future

Abstract Class or Interface Class...Which will you decide

This is an interview question asked by one of the interviewee..

Answer pls..

Posted 5-Sep-14 21:05pm

sahmed3

Add a Solution

Comments

Mehdi Gholam 6-Sep-14 3:22am

It depends on what you are doing and how you are doing it.

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

sharathkumarkr · Answer 1 · 2014-09-05T21:24:00

Solution 1

[^]

Posted 5-Sep-14 21:24pm

sharathkumarkr

CPallini · Answer 2 · 2014-09-05T21:32:00

Solution 2

Short answer: Interfaces are for architects, Abstract Classes are for coders.
Long answer: it really depends on the scenario (and on the lack of multiple inheritance of C#). Check out a good OOP book in order to tell the difference.

Posted 5-Sep-14 21:32pm

CPallini

OriginalGriff · Answer 3 · 2014-09-05T21:40:00

It's not a "either / or" situation: they are very different beasties.
An abstract class is an "almost complete" class that requires the derived class to "fill in the blanks" but allows you to provide code which is common to all derived classes.
An Interface doesn't: it allows you to specify a contract which the implementing class must complete, but which can provide no code at all.

You can derive from a class and implement an unspecified number of interfaces at the same time, but you can only derive from a single abstract class.

It's like the difference between a Fruit (abstract class) and IDrive (Interface) - the former allows you to derive Apple and Pear classes, while the latter allows you to use a car to get from A to B. A Fruit exists; IDrive is a process that you can't hold in your hand.