class Aeroplane : IFlyable, IFuelable, IMachine
{ // Aeroplane's Design says:
  // Aeroplane is a flying object
  // Aeroplane can be fueled
  // Aeroplane is a Machine
}
// But the code related to Pilot, or Driver of Aeroplane is not bothered 
// about Machine or Fuel. Hence,
// pilot code:
IFlyable flyingObj = new Aeroplane();
flyingObj.Fly();
// fighter Pilot related code
IFlyable flyingObj2 = new FighterAeroplane();
flyingObj2.Fly();
// UFO related code 
IFlyable ufoObj = new UFO();
ufoObj.Fly();
// **All the 3 Above codes are genaralized using IFlyable,
// Interface Abstraction**
// Fly related code knows how to fly, irrespective of the type of 
// flying object they are.

// Similarly, Fuel related code:
// Fueling an Aeroplane
IFuelable fuelableObj = new Aeroplane();
fuelableObj.FillFuel();
// Fueling a Car
IFuelable fuelableObj2 = new Car(); // class Car : IFuelable { }
fuelableObj2.FillFuel();

// ** Fueling code does not need know what kind of vehicle it is, so far 
// as it can Fill Fuel**

抽象或封装并不严格要求信息隐藏。信息可能会被忽略，但不一定要隐藏。

封装是一种将事物视为单一事物的能力，即使它可能由许多复杂的部分或思想组成。例如，我可以说我坐在一把“椅子”上，而不是指这把椅子上的许多不同部分，每个部分都有特定的设计和功能，它们精确地组合在一起，目的是让我的屁股舒适地离地板几英尺远。

Abstraction is enabled by encapsulation. Because we encapsulate objects, we can think about them as things which relate to each other in some way rather than getting bogged down in the subtle details of internal object structure. Abstraction is the ability to consider the bigger picture, removed from concern over little details. The root of the word is abstract as in the summary that appears at the top of a scholarly paper, not abstract as in a class which can only be instantiated as a derived subclass.

I can honestly say that when I plop my butt down in my chair, I never think about how the structure of that chair will catch and hold my weight. It's a decent enough chair that I don't have to worry about those details. So I can turn my attention toward my computer. And again, I don't think about the component parts of my computer. I'm just looking at a part of a webpage that represents a text area that I can type in, and I'm communicating in words, barely even thinking about how my fingers always find the right letters so quickly on the keyboard, and how the connection is ultimately made between tapping these keys and posting to this forum. This is the great power of abstraction. Because the lower levels of the system can be trusted to work with consistency and precision, we have attention to spare for greater work.

封装意味着隐藏数据，比如使用getter和setter等。

抽象意味着-隐藏实现使用抽象类和接口等。

封装隐藏了实现细节，这些细节可能是通用的，也可能不是专门的行为。

抽象提供了一种泛化(例如，在一组行为之上)。

这里有一个很好的阅读:抽象、封装和信息隐藏，作者是Object Agency的Edward V. Berard。

另一个例子:

假设我创建了一个不可变的Rectangle类，如下所示:

class Rectangle {
 public:
  Rectangle(int width, int height) : width_(width), height_(height) {}
  int width() const { return width_; }
  int height() const { return height_; }

 private:
  int width_;
  int height_;
}

现在很明显，我已经封装了宽度和高度(访问受到某种限制)，但我没有抽象任何东西(好吧，也许我忽略了矩形在坐标空间中的位置，但这是示例的缺陷)。

好的抽象通常意味着好的封装。

一个好的抽象例子是通用数据库连接类。它的公共接口与数据库无关，非常简单，但允许我对连接做我想做的事情。你看到了吗?这里还有封装，因为类内部必须有所有低级句柄和调用。

抽象让您关注对象做了什么，而不是它是如何做的 封装意味着隐藏对象如何做某事的内部细节或机制。

就像你开车时，你知道油门踏板的作用，但你可能不知道它背后的过程，因为它是封装的。

让我用c#举个例子。假设你有一个整数:

int Number = 5;
string aStrNumber = Number.ToString();

你可以使用像number . tostring()这样的方法，它返回数字5的字符表示，并将其存储在字符串对象中。该方法告诉您它做了什么，而不是如何做。