This is a strange behavior. The C++ compiler, when given the two dimensional array [1, 2, 3] as a single parameter, returns the error message: “array set to zero”.
This is most likely a bug in the debugger. If you have an array of 2D array objects with an index of 0, you may get the error message: array set to zero. In debug mode, the debugger will probably just print the array and quit.
You can probably fix this by passing 0x0 for the array index.
It’s always better to have the array initialized to zero. In the debugger, the debugger will check for the value of the parameter.
C++ has a few weirdnesses. The array index 0 is not a special keyword, it’s a number. The array index 1 is also a number, but it’s not a special keyword. That means you can pass 2, 3, 4, or any other number, and it will still be a number.
You can be certain that the debugger doesn’t actually try to print anything that’s not a pointer. The debugger can’t do that, and it should not throw an exception to that. The debugger has a reason to print anything. If you want to print whatever you want to, you can just write it to the console.
The debugger doesn’t throw an exception so the array index 1 will be 0x0, and the array index 2 will be 1×0. It’s really bad, because it’s kind of like having a console on a computer, but it’s not really so bad if you’ve got the debugger running and it’s running on the console.
If you’re using a debugger, you should probably do things like set breakpoints and go to them. Otherwise, what’s the point? The only reason c++ programmers use the debugger is because they are usually the ones that will keep track of memory access, so if you dont tell them to break or step through something, it doesn’t matter.
So, what does a debugger do? It basically lets you go to specific locations in memory to debug. And it lets you specify which variables you want to look at/print. It is also good for the programmer to take care of the fact that they are running on a machine that is not as fast as their own. Because if the machine is fast enough, the debugger will let you step through variables you didnt even think were there.
