简而言之

抽象使用->封装 ＆ 封装使用->数据隐藏

OR

数据隐藏是封装和的子集 封装是抽象的一个子集

参考:http://www.tonymarston.co.uk/php-mysql/abstraction.txt

下面这段话帮助我理解了它们之间的区别:

数据封装是一种捆绑数据的机制 使用它们的函数和数据抽象是一种机制 只暴露接口，隐藏实现细节 来自用户。

你可以在这里阅读更多。

抽象是我们将要执行的实现的契约。实现可能会在一段时间内发生变化。各种实现本身可能隐藏，也可能不隐藏，而是隐藏在抽象后面。

假设我们在一个接口中定义了一个类的所有api，然后要求代码的用户依赖于该接口中定义的api。我们可以自由地改进或修改实现，但必须遵守设定的合同。用户与我们的实现没有耦合。

我们在抽象中暴露所有必要的规则(方法)，规则的实现留给实现者实体，实现也不是抽象的一部分。正是签名和声明使抽象成为现实。

封装只是通过减少对状态和行为的访问来隐藏内部细节。封装的类可能有也可能没有定义良好的抽象。

java.util.List是java.util.ArrayList的抽象。使用非公共访问修饰符标记的java.util.ArrayList的内部状态是封装。

Edit Suppose a class Container.nava implements IContainer , IContainer may declare methods like addElement, removeElements, contains, etc. Here IContainer represents the abstraction for its implementing class. Abstraction is declaring the APIs of the class or a module or a system to the outer world. These APIs become the contract. That system may be or may not be developed yet. The users of the system now can depend on the declared APIs and are sure any system implementing such a contract will always adhere to the APIs declared, they will always provide tge implementation for those APIs. Once we are writing some concrete entity then deciding to hide our internal states is encapsulation

一种防止特定对象的数据被外部函数故意或意外误用的机制叫做“数据封装”。

在不包括背景细节或解释的情况下表现基本特征的行为被称为抽象

另一个例子:

假设我创建了一个不可变的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_;
}

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

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

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

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

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

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.