compiler problem

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

DR - 02 Sep 2005 22:36 GMT

void a()
{
for (int i = 0; i <100; i++)
{
...
}
...
for (i = 0; i <100; i++) <-- ERROR
{
...
}
}

The VC++ 2005 compilers says "i undeclared identifer". Why?

Reply to this Message

sashan - 02 Sep 2005 22:52 GMT

i is out of scope after the end of the first for loop. There was a time
when some compilers would allow i to be in scope after the 1st for loop
had ended but the C++ standard (see section 6.5.3) does not allow this
behaviour any more. You can tell the compiler using /Ze that you want i
to be in scope after the end of the loop. Personally I would change my
code so that it was standard compliant.

--
sashan
http://sashang.orcon.net.nz/index.htm

Reply to this Message

Jonathan Caves - 03 Sep 2005 01:44 GMT

>i is out of scope after the end of the first for loop. There was a time
> when some compilers would allow i to be in scope after the 1st for loop
[quoted text clipped - 6 lines]
> sashan
> http://sashang.orcon.net.nz/index.htm

In Visual C++ 2005 the option to revert back to the old non-conformant
behavior is:

/Zc:forScope-

Signature

Jonathan Caves
Visual C++ Compiler Team

Reply to this Message

DR - 03 Sep 2005 04:21 GMT

> In Visual C++ 2005 the option to revert back to the old non-conformant
> behavior is:
>
> /Zc:forScope-

I figured that out.

I'll report a bug:
The /W0 option seams to be ignored by the VC++2005Exp compiler . I still get
warnings.

Reply to this Message

compiler problem

Free Magazines