When you try to draw something on the screen, your code calls some other piece of code which calls some other code (etc.) until finally there is a "system call", which is a special instruction that the CPU can execute. These instructions can be either written in assembly or can be written in C++ if the compiler supports their "intrinsics" (which are functions that the compiler handles "specially" by converting them into special code that the CPU can understand). Their job is to tell the operating system to do something.

When a system call happens, a function gets called that calls another function (etc.) until finally the display driver is told to draw something on the screen. At that point, the display driver looks at a particular region in physical memory which is actually not memory, but rather an address range that can be written to as if it were memory. Instead, however, writing to that address range causes the graphics hardware to intercept the memory write, and draw something on the screen. Writing to this region of memory is something that could be coded in C++, since on the software side it's just a regular memory access. It's just that the hardware handles it differently. So that's a really basic explanation of how it can work.

When you try to draw something on the screen, your code calls some other piece of code which calls some other code (etc.) until finally there is a "system call", which is a special instruction that the CPU can execute. These instructions can be either written in assembly or can be written in C++ if the compiler supports their "intrinsics" (which are functions that the compiler handles "specially" by converting them into special code that the CPU can understand). Their job is to tell the operating system to do something.

When a system call happens, a function gets called that calls another function (etc.) until finally the display driver is told to draw something on the screen. At that point, the display driver looks at a particular region in physical memory which is actually not memory, but rather an address range that can be written to as if it were memory. Instead, however, writing to that address range causes the graphics hardware to intercept the memory write, and draw something on the screen. Writing to this region of memory is something that could be coded in C++, since on the software side it's just a regular memory access. It's just that the hardware handles it differently. So that's a really basic explanation of how it can work.

硬件是允许这一切发生的原因。您可以将图形存储器看作一个大数组(由屏幕上的每个像素组成)。要绘制到屏幕上，您可以使用c++或任何允许直接访问该内存的语言写入该内存。该内存恰好可以被显卡访问或位于显卡上。

在现代系统中，由于各种限制，直接访问图形存储器需要编写驱动程序，因此您可以使用间接方法。库创建一个窗口(实际上只是一个像其他图像一样的图像)，然后将该图像写入图形内存，然后GPU将其显示在屏幕上。除了写入特定内存位置的能力之外，该语言不需要添加任何东西，这就是指针的作用。

为了提供与其他答案略有不同的观点，我将这样回答。

(免责声明:我只是稍微简化了事情，我给出的情况纯粹是假设的，是作为演示概念的一种手段而写的，而不是100%真实的生活)。

从另一个角度考虑问题，假设您刚刚编写了一个简单的操作系统，具有基本的线程、窗口和内存管理功能。你想要实现一个c++库，让用户用c++编程，做一些事情，比如创建窗口，在窗口上绘图等等。问题是，如何做到这一点。

首先，由于c++编译为机器代码，您需要定义一种使用机器代码与c++进行接口的方法。这就是函数的作用所在，函数接受参数并给出返回值，因此它们提供了在不同代码段之间传输数据的标准方式。他们通过建立一种称为调用约定的东西来做到这一点。

A calling convention states where and how arguments should be placed in memory so that a function can find them when it gets executed. When a function gets called, the calling function places the arguments in memory and then asks the CPU to jump over to the other function, where it does what it does before jumping back to where it was called from. This means that the code being called can be absolutely anything and it will not change how the function is called. In this case however, the code behind the function would be relevant to the operating system and would operate on the operating system's internal state.

所以，几个月后，你已经整理好了所有的操作系统功能。你的用户可以调用函数来创建窗口并在上面绘图，他们可以创建线程和所有美妙的东西。但问题是，你的操作系统的功能将不同于Linux或Windows的功能。所以你决定给用户一个标准的界面，这样他们就可以编写可移植的代码。这就是QT的用武之地。

As you almost certainly know, QT has loads of useful classes and functions for doing the sorts of things that operating systems do, but in a way that appears independent of the underlying operating system. The way this works is that QT provides classes and functions that are uniform in the way they appear to the user, but the code behind the functions is different for each operating system. For example QT's QApplication::closeAllWindows() would actually be calling each operating system's specialised window closing function depending on the version used. In Windows it would most likely call CloseWindow(hwnd) whereas on an os using the X Window System, it would potentially call XDestroyWindow(display,window).

很明显，操作系统有很多层，所有这些层都必须通过各种各样的接口进行交互。有许多方面我还没有谈到，但要全部解释它们将需要很长时间。如果您对操作系统的内部工作原理有进一步的兴趣，我建议您查看OS dev wiki。

请记住，许多操作系统选择向C/ c++公开接口的原因是它们可以编译为机器代码，它们允许将汇编指令与它们自己的代码混合在一起，并且它们为程序员提供了很大程度的自由。

同样，这里有很多内容。我想继续解释库如何像.so和.dll文件不需要用C/ c++编写，可以用汇编或其他语言编写，但我觉得如果我再添加更多，我还不如写一整篇文章，尽管我很想这样做，但我没有一个站点来托管它。

首先，我觉得有一点误会

c++以前没有语法能够要求操作系统提供一个窗口或一种通过网络通信的方式，它是如何做到的呢

没有用于操作系统操作的语法。这是语义学的问题。

突然通过c++本身编写的库获得这些功能

操作系统主要是用c编写的。您可以使用共享库(即dll)来调用外部代码。此外，操作系统代码可以在系统调用*或中断上注册系统例程，您可以使用程序集调用这些例程。共享库通常只是为您进行系统调用，因此您可以避免使用内联汇编。

这里有一个很好的教程:http://www.win.tue.nl/~aeb/linux/lk/lk-4.html 它适用于Linux，但原理是相同的。

操作系统如何对显卡、网卡等进行操作?这是一个非常广泛的主题，但大多数情况下你需要访问中断，端口或写入一些数据到特殊的内存区域。由于这些操作是受保护的，所以无论如何都需要通过操作系统调用它们。

好问题。每一个新的C或c++开发人员都有这样的想法。在本文的其余部分中，我假设使用的是标准的x86机器。如果你使用的是微软c++编译器，打开你的记事本并输入这个(命名为Test.c)

int main(int argc, char **argv)
{
   return 0
}

现在编译这个文件(使用开发人员命令提示符)cl Test.c /FaTest.asm

现在打开Test。在你的记事本里。你看到的是翻译后的代码——C/ c++被翻译成汇编程序。你明白我的意思了吗?

_main   PROC
    push    ebp
    mov ebp, esp
    xor eax, eax
    pop ebp
    ret 0
_main   ENDP

C/ c++程序是设计来在金属上运行的。这意味着他们可以访问较低级别的硬件，从而更容易利用硬件的功能。比如说，我要在x86机器上编写一个C库getch()。

根据汇编器的不同，我可以这样输入:

_getch proc 
   xor AH, AH
   int 16h
   ;AL contains the keycode (AX is already there - so just return)
ret

我用汇编程序运行它并生成一个。obj -命名为getch.obj。

然后我写了一个C程序(我不包括任何东西)

extern char getch();

void main(int, char **)
{
  getch();
}

现在将这个文件命名为GetChTest.c。通过传递getch来编译这个文件。obj。(或者单独编译到.obj和LINK GetChTest。Obj和getch。Obj一起生成GetChTest.exe)。

运行GetChTest.exe，你会发现它在等待键盘输入。

C/C++ programming is not just about language. To be a good C/C++ programmer you need to have a good understanding on the type of machine that it runs. You will need to know how the memory management is handled, how the registers are structured, etc., You may not need all these information for regular programming - but they would help you immensely. Apart from the basic hardware knowledge, it certainly helps if you understand how the compiler works (ie., how it translates) - which could enable you to tweak your code as necessary. It is an interesting package!

这两种语言都支持__asm关键字，这意味着你也可以混合汇编语言代码。学习C和c++会让你成为一个更全面的程序员。

不需要总是与汇编程序链接。我提到它是因为我认为这会帮助你们更好地理解。大多数这样的库调用都利用了操作系统提供的系统调用/ api(操作系统负责硬件交互)。