Thread: for( int i = 0; i < 5; i++ )

Code:

for( int i = 0; i < 5; i++ )
{
      cout << "You suck!!!" << endl;
}

for( int i = 0; i < 5; i++ )
{
      cout << "You suck!!!" << endl;
}

That is possible in Java but in C++ you have to do this way:

Code:

for( int i = 0; i < 5; i++ )
{
      cout << "You suck!!!" << endl;
}

for( int j = 0; j < 5; j++ )
{
      cout << "You suck!!!" << endl;
}

or

Code:

int i;
for( i = 0; i < 5; i++ )
{
      cout << "You suck!!!" << endl;
}

for( i = 0; i < 5; i++ )
{
      cout << "You suck!!!" << endl;
}

C++ approach for this problem sucks. So is there any reason for this annoying problem? Is this a C++ bug???

Please, guyz!!! I am not Java troll........

oh, yeah, you right. I never check it before. I thought it cann't because variable i cannot be use after for statement.

The dumbest post I have ever made.

Ok, since I made the dumbest post, I have to fix it. Consider this code:

Code:

#include <iostream>
using namespace std;

int main()
{
   for( int i = 0; i < 4; i++ )
   {
      cout << "You suck" << endl;
   }

   f = 9;
}

You got this error:
test.cpp: In function `int main()':
test.cpp:11: error: `f' undeclared (first use this function)
test.cpp:11: error: (Each undeclared identifier is reported only once for each
function it appears in.)
This is logic just as in Java with this code:

Code:

public class Tess
{
   public static void main( String[] args )
   {
      for( int i = 0; i < 4; i++ )
      {
         System.out.println( "Damned" );
      }
      f = 9;
   }
}

You got this error. Just same with C++. Only different language.
Tess.java:9: cannot resolve symbol
symbol : variable f
location: class Tess
f = 9;
^
1 error
But if you use this code:

Code:

#include <iostream>
using namespace std;

int main()
{
   for( int i = 0; i < 4; i++ )
   {
      cout << "You suck" << endl;
   }

   i = 9;
}

You got unusual error. You didn't get this error:
test.cpp: In function `int main()':
test.cpp:11: error: `i' undeclared (first use this function)
test.cpp:11: error: (Each undeclared identifier is reported only once for each
function it appears in.)
But you got this error:
test.cpp: In function `int main()':
test.cpp:11: error: name lookup of `i' changed for new ISO `for' scoping
test.cpp:6: error: using obsolete binding at `i'

But in Java, the error is still the same with this code:

Code:

public class Tess
{
   public static void main( String[] args )
   {
      for( int i = 0; i < 4; i++ )
      {
         System.out.println( "Damned" );
      }
      i = 9;
   }
}

Tess.java:9: cannot resolve symbol
symbol : variable i
location: class Tess
i = 9;
^
1 error

Is there any good reason C++ handle this i different than Java?

Originally Posted by gandalf_bar

oh, yeah, you right. I never check it before. I thought it cann't because variable i cannot be use after for statement.

The dumbest post I have ever made.

I'll have to agree. Dumbest. Post Ever. You start a thread to complain about a problem that you haven't even compiled to see if it exists? What, you just made up some s... to complain about, even though you had never even TRIED to compile your supposed "C++ bug".

Not a java troll? Maybe. But definately a dumbass.

Quzah.

all your c++ compiler is saying to you is that it sees that you are trying to use an out of scope variable and the java one isn't

Originally Posted by gandalf_bar

Is there any good reason C++ handle this i different than Java?

Yeah, one is C++ and one is Java. Two different languages.

Quzah.

Hey, quzah...... take it easy.....
please look at the post before your post.......
calm down. There is no need to waste energy with my dumbness.

Actually, it WAS the case that the original code would have a problem - the new C++ standard changed the scope rules in this particular instance.

That's why GCC has this handy compiler option

-ffor-scope
-fno-for-scope
If -ffor-scope is specified, the scope of variables declared in a for-init-statement is limited to the for loop itself, as specified by the C++ standard. If -fno-for-scope is specified, the scope of variables declared in a for-init-statement extends to the end of the enclosing scope, as was the case in old versions of G++, and other (traditional) implementations of C++.

Thank you, guyz! Now I understand it very much......