这里的大多数答案都关注于OOP，但封装开始得更早:

Every function is an encapsulation; in pseudocode: point x = { 1, 4 } point y = { 23, 42 } numeric d = distance(x, y) Here, distance encapsulates the calculation of the (Euclidean) distance between two points in a plane: it hides implementation details. This is encapsulation, pure and simple. Abstraction is the process of generalisation: taking a concrete implementation and making it applicable to different, albeit somewhat related, types of data. The classical example of abstraction is C’s qsort function to sort data: The thing about qsort is that it doesn't care about the data it sorts — in fact, it doesn’t know what data it sorts. Rather, its input type is a typeless pointer (void*) which is just C’s way of saying “I don't care about the type of data” (this is also called type erasure). The important point is that the implementation of qsort always stays the same, regardless of data type. The only thing that has to change is the compare function, which differs from data type to data type. qsort therefore expects the user to provide said compare function as a function argument.

封装和抽象是密切相关的，因此您可以认为它们确实是不可分割的。就实际而言，这可能是对的;也就是说，这里有一个不太抽象的封装:

class point {
    numeric x
    numeric y
}

我们封装了点的坐标，但是我们没有实质性地将它们抽象出来，只是在逻辑上对它们进行分组。

这里有一个抽象的例子，它不是封装:

T pi<T> = 3.1415926535

这是一个具有给定值(π)的泛型变量pi，声明并不关心变量的确切类型。诚然，我很难在真实的代码中找到这样的东西:抽象实际上总是使用封装。然而，上面的内容在c++(14)中确实存在，通过变量模板(=变量的通用模板);使用稍微复杂一点的语法，例如:

template <typename T> constexpr T pi = T{3.1415926535};

抽象:抽象的意思是显示功能的哪一部分。

封装:封装意味着隐藏功能的How部分。

让我们举一个非常简单的例子

/// <summary>
/// We have an Employee class having two properties EmployeeName and EmployeeCode
/// </summary>
public class Employee
{
    public string EmplpyeeName { get; set; }
    public string EmployeeCode { get; set; }

    // Add new employee to DB is the main functionality, so are making it public so that we can expose it to external environment
    // This is ABSTRACTION
    public void AddEmployee(Employee obj)
    {
        // "Creation of DB connection" and "To check if employee exists" are internal details which we have hide from external environment
        // You can see that these methods are private, external environment just need "What" part only
        CreateDBConnection();
        CheckIfEmployeeExists();
    }


    // ENCAPLUSATION using private keyword
    private bool CheckIfEmployeeExists()
    {
        // Here we can validate if the employee already exists
        return true;
    }

    // ENCAPLUSATION using private keyword
    private void CreateDBConnection()
    {
        // Create DB connection code
    }
}

控制台应用程序程序类

class Program
{
    static void Main(string[] args)
    {
        Employee obj = new Employee();
        obj.EmplpyeeName = "001";
        obj.EmployeeCode = "Raj";

        // We have exposed only what part of the functionality
        obj.AddEmployee(obj);
    }
}

我读得越多，就越困惑。所以，我的理解是:

封装:

我们通常从外面看到手表，它的组件被封装在它的身体里。我们对不同的操作有某种控制。这种隐藏细节和公开控制(例如设置时间)的方式就是封装。

抽象:

到目前为止，我们一直在谈论手表。但我们没有具体说明是哪种手表。可以是数字的，也可以是模拟的，可以是手用的，也可以是墙用的。有很多可能性。我们所知道的是，这是一块手表，它显示时间，这是我们唯一感兴趣的东西，时间。这种隐藏细节和公开通用特性或用例的方法就是抽象。

封装把一些东西放在一个盒子里，给你一个窥视孔;这使你从混乱与齿轮。

抽象完全忽略了无关紧要的细节，比如物体是否有齿轮、棘轮、飞轮或核心;他们只是“走了”

封装的例子:

内裤 工具箱 钱包 手提包 胶囊 冷冻carbonite 一个盒子，上面有或没有按钮 一个墨西哥卷饼(严格来说，是卷饼周围的玉米粉圆饼)

抽象的例子:

“一组事物”是一种抽象(我们称之为聚合) “包含其他事物的事物”是一种抽象(我们称之为组合) “容器”是另一种“物装物”的抽象;注意，所有的封装示例都是不同种类的容器，但并不是所有的容器都展示/提供封装。例如，篮子是一种不封装其内容的容器。

封装是抽象的一个例子。封装的全部意义在于抽象函数内部发生的事情，将所有的复杂性简化为一个符号(函数的引用或名称)，将函数变成一个黑盒。

在编程中，“抽象”一词是一个命令。当一个类继承了一个抽象类(或接口)时，您将被命令创建一个抽象。

封装:对对象的实际用户隐藏不需要的/不期望的/适当的实现细节。 如。

List<string> list = new List<string>();
list.Sort(); /* Here, which sorting algorithm is used and hows its 
implemented is not useful to the user who wants to perform sort, that's 
why its hidden from the user of list. */

抽象:是一种提供泛化的方法，因此是处理大量不同对象的通用方法。如。

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**