该楼层疑似违规已被系统折叠 隐藏此楼查看此楼
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.