//construct one string from another
Why C++ does does not provide any bound checkings:
You might be wondering why C++ does not provide boundary checks on arrays. The answer is that C++ was designed to give professional programmers the capability to create the fastest, most efficient code possible. Towards this end, virtually no run-time error checking is included because it slows (often dramatically) the execution of a program. Instead, C++ expects you, the programmer, to be responsible enough to prevent array overruns in the first place and to add appropriate error checking on your own, as needed.
C++ performs no bounds checking, nothing stops you from overrunning the end of an array. If this happens during an assignment operation, you will be assigning values to some other variable’s data, or even into a piece of the program’s code. In other words, you can index an array of size N beyond N without causing any compiler run-time error messages, even though doing so will probably cause your program to crash. As the programmer, it is your job both to ensure that all arrays are large enough to hold what the program will put in them and to provide bounds checking whenever necessary.
For example, C++ will compile and run the following program even though the crash is being overrun
// An incorrect program. Do Not Execute!
int main()
{
int crash[10], i;
for(i=0; i<100; i++)
crash[i] = i; // Error! array overrun
return 1;
}
In this case, the loop will iterate 100 times, even though the array crash is only ten elements long! This might cause important information to be overwritten, resulting in a program failure.
You might be wondering why C++ does not provide boundary checks on arrays. The answer is that C++ was designed to give professional programmers the capability to create the fastest, most efficient code possible. Towards this end, virtually no run-time error checking is included because it slows (often dramatically) the execution of a...