According to the Wikipedia (http://en.wikipedia.org/wiki/Buffer_overflow)
Programming languages commonly associated with buffer overflows include C and C++, which provide no built-in protection against accessing or overwriting data in any part of memory and do not automatically check that data written to an array (the built-in buffer type) is within the boundaries of that array. Bounds checking can prevent buffer overflows.
So, why are ‘Bounds Checking’ not implemented in some of the languages like C and C++?
Basically, it’s because it means every time you change an index, you have to do an if statement.
Let’s consider a simple C for loop:
if we have bounds checking, the generated code for
ary[ix]has to be something likeIf we don’t have that bounds check, then we can write instead:
This saves 3-4 instructions in the loop, which (especially in the old days) meant a lot.
In fact, in the PDP-11 machines, it was even better, because there was something called “auto-increment addressing”. On a PDP, all of the register stuff etc turned into something like
(And anyone who happens to remember the PDP better than I do, don’t give me trouble about the precise syntax etc; you’re an old fart like me, you know how these things slip away.)