抽象类或接口。 哪种方式是正确的？

Question

There are two way for choosing between abstract class or interface. Microsoft solution and Oracle solution:

---

Microsoft, design guideline:

Do use abstract (MustInherit in Visual Basic) classes instead of interfaces to decouple the contract from implementations.

http://msdn.microsoft.com/en-us/library/ms229013.aspx

---

Oracle, The Java Tutorials:

If an abstract class contains only abstract method declarations, it should be declared as an interface instead.

http://docs.oracle.com/javase/tutorial/java/IandI/abstract.html

---

My question is which way is correct? Microsoft or Oracle solution? Note that I think choose between abstract class or interface should not depends on programming language (Java or C#).

Answer 1

If I recall my blog reading correctly, the Microsoft advice to use abstract classes stems from the ability to reuse implementation with an abstract class, something you can't do with an interface.

Note also that the Microsoft page you linked to is specifically guidance for writing code libraries for sharing/reuse across multiple projects. The likelihood in this situation is that you'll be writing all the implementations of the interface yourself, probably within the same assembly. Good practices for working on a single product or system will vary somewhat.

One common approach that I've seen across a number of codebases in a number of languages is this:

• Define an interface to specify the contract
• Create an abstract class implementing the contract to provide any common implementation useful to all descendants
• Implementations of the contract then have the option to start from the base class for convenience, or just to implement the interface if they want full control

A fourth step common in the .NET world is to provide convenience extension functions built on the interface.

Answer 2

They are 2 statements for different contexts.

The Microsoft guideline you quote from is for "Designing Class Libraries". And it states the reason for favoring abstract classes there: you can add functionality without breaking anything.

For separation and decoupling over layers and other boundaries, Microsoft also advices interfaces.

Answer 3

An interface carries no implementation - it's a contract. It allows for complete decoupling.

I will go from an interface to an abstract (base) class if I want to provide some common implementation while forcing on the inheriting class concrete class to provide some implementation specific to that class. That's provides a little less decoupling.

Also be aware that many languages like C# (and .net languages like VB.net etc...) as well as Java do not allow multiple inheritance so interfaces become a way of allowing a class to have many behaviors.