这篇博客探讨了C语言中指针和数组下标的检查问题。由于标准并未强制要求进行下标检查，早期及许多当前的C编译器都不进行这种检查，这给编程带来了一定的挑战。指针可以应用于任意指针，而非仅限于数组名，使得验证下标有效性变得复杂。检查指针下标是否有效的过程涉及额外的运行时开销，需要存储所有数组的位置和大小信息，并在程序运行时更新，以处理自动和动态分配的数组。
该楼层疑似违规已被系统折叠 隐藏此楼查看此楼
C和指针，8.1.2
The last two examples show why subscript checking is a difficult task in C.
The standard does not require that it be done at all; the earliest C compilers didn*t check subscripts, and most current ones still don*t.
The fact that subscripts can be applied to arbitrary pointers, not just array names, makes the job difficult.
The validity of a subscript applied to a pointer variable depends on where it happens to be pointing at the time, as well as the value of the subscript.
Consequently, subscript checking in C involves more overhead than you might first think.
Instructions must be inserted into the program to verify that the result of the subscript refers to an element in the same array as the pointer.
This comparison requires information about the locations and sizes of all arrays in the program, which will take some space.
The information must also be updated as the program runs to reflect automatic and dynamically allocated arrays, which will take some time.
扫一扫
1691
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
