[RESOLVED] MS VC++ Error?

[Rick Bull]

Hi, I'm new to C++, and I was just testing out arrays. I made a 2D array, and had the following code to get the user to fill the arrays, and then read it back:

for (USINT loopcounter1 = 0; loopcounter1 < 3; loopcounter1++)
	{
		for (USINT loopcounter2 = 0; loopcounter2 < 3; loopcounter2++)
		{
			cout << "Please enter a number for " <<
				"[" << loopcounter1 << "]" <<
				"[" << loopcounter2 << "]: ";
			cin >> numbers[loopcounter1][loopcounter2];
		}
	}
	cout << "Thank you\n";
	for (USINT loopcounter1 = 0; loopcounter1 < 3; loopcounter1++)
	{
		for (USINT loopcounter2 = 0; loopcounter2 < 3; loopcounter2++)
		{
			cout << "Item [" << loopcounter1 << "]" <<
				"[" << loopcounter2 << "] = " <<
				numbers[loopcounter1][loopcounter2] <<
				endl;
		}
	}

But Microsoft Visual C++ gave me a compile error at the bolded text that USINT loopcounter1 had already been declared on the first loop. I may be wrong here but I should declare it again shouldn't I as it's gone out of scope and has been destroyed. I compiled the same prog in Dev-C++ and it compiled without an error, who's right?

[jim mcnamara]

Try UINT

[CornedBee]

That's a thing that recently changed in the standard.
In early C++ standards a variable declared inside a for-statement:
for(int i=0;...)
was supposed to be in the surrounding scope. Since a recent change it is supposed to be in the inner scope, the one between the brackets of the for-statement.

But to be honest, even VC++7 follows the old standard. To be on the safe side it is usually best to declare loop variables once at the start of the function (like in C) and be done with it.

[Rick Bull]

Oh thanks guys. I've found a few things I've thought to be bugs, but I assume that it's just that VC++ isn't ANSI standard, is that right?

And the USINT is a typedef I made at the top of the program, just thought it was all irrelevant so I cut it