Visual .NET not complaining on a C++ semantic error

[lamthierry]

I have the following piece of codes:


for (int i = 0; i < 10; i++)
function1();

for (i = 0; i < 5; i++)
function2();


Technically, I should be getting an error in the 2nd for loop but when
I compile the above with Visual .NET, everything compiles fine.

Any ideas what's wrong? I did not define I globally elsewhere.

Thanks
Thierry

 

[Victor Bazarov]

I have the following piece of codes:


for (int i = 0; i < 10; i++)
function1();

for (i = 0; i < 5; i++)
function2();


Technically, I should be getting an error in the 2nd for loop but when
I compile the above with Visual .NET, everything compiles fine.

Any ideas what's wrong? I did not define I globally elsewhere.

You need to learn to use your compiler better. By default it has this
"feature" as an "extension". Disable language extensions and you'll get
an error message. Also, consider asking compiler-specific questions in
a newsgroup for that compiler (microsoft.public.vc.language, here)

V

 

[Maxim Yegorushkin]

I have the following piece of codes:


for (int i = 0; i < 10; i++)
function1();

for (i = 0; i < 5; i++)
function2();


Technically, I should be getting an error in the 2nd for loop but when
I compile the above with Visual .NET, everything compiles fine.

Any ideas what's wrong? I did not define I globally elsewhere.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/vcrefzcforscope.asp

 

[Bob Hairgrove]

I have the following piece of codes:


for (int i = 0; i < 10; i++)
function1();

for (i = 0; i < 5; i++)
function2();


Technically, I should be getting an error in the 2nd for loop but when
I compile the above with Visual .NET, everything compiles fine.

Any ideas what's wrong? I did not define I globally elsewhere.

Thanks
Thierry

There have been many times when I wished I could redefine "I" globally
elsewhere...<g>.

Seriously, though, I would first look for a compiler switch which
turns off the ANSI "for" scope rules regarding the above.

Secondly, I suspect pollution of the global namespace as the culprit.
I would look for any header files, included either directly or
indirectly by your own headers (but including your own headers) which
have "using namespace <whatever>;" in them. One of these MIGHT have
declared "i" at global scope within the local namespace or else at
global scope.

Other than that -- well, perhaps you *did* declare an "i" (or was it
an "I"?? <g>) somewhere at global scope...

 

[Karl Heinz Buchegger]

I have the following piece of codes:

for (int i = 0; i < 10; i++)
function1();

for (i = 0; i < 5; i++)
function2();

Technically, I should be getting an error in the 2nd for loop but when
I compile the above with Visual .NET, everything compiles fine.

Any ideas what's wrong? I did not define I globally elsewhere.

Any chance you are using Visual C++ 6.0 compiler?
That compiler had that 'bug'. Microsoft had a 'good reason' keep that
old way of treating loop variables. It can be changed by a compiler switch.

AFAIK, later versions of VC compilers changed that.

 

[lamthierry]

Thanks, that helps, I wasn't aware of that.

Thierry

 

[Ook]

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/vcrefzcforscope.asp

That is exactly what it was. Project Properties -> Configuration
Properties -> c/c++ -> Language -> Force Conformance In For Loop Scope
defaults to No. Ack, I wonder how many mistakes I made in my code because I
didn't know about this?

 

[Guest]

Im using 2005b2, default config

error C2065: 'i' : undeclared identifier

you have prob messed up something. vs isnt so ...stupid

 

[Maxim Yegorushkin]

Karl Heinz Buchegger wrote:

[]

Any chance you are using Visual C++ 6.0 compiler?
That compiler had that 'bug'. Microsoft had a 'good reason' keep that
old way of treating loop variables. It can be changed by a compiler switch.

Visual C++ 6.0 does not have a switch for that.

The usual solution for this compiler was:

#define for if(0); else for

 

[Victor Bazarov]

Karl Heinz Buchegger wrote:

[]

Any chance you are using Visual C++ 6.0 compiler?
That compiler had that 'bug'. Microsoft had a 'good reason' keep that
old way of treating loop variables. It can be changed by a compiler
switch.

Visual C++ 6.0 does not have a switch for that.

Actually, it does. It's called "Disable Language extensions". OT here,
but still. Of course, it causes all kinds of trouble if you try to use
some other MS libraries...

[...]

V