goto

[Novo]

goto's are only useful ( really ) when you want to break out of two loop controls. They are quite obfuscating otherwise. Additionally, there are numerous reports telling us that the more goto's there are in a code, the higher the complexity is.

Plus... There'd be quite a bit of problems with the environment change ( change in function / object / scope ). It's best not to use it at all... In ANY language -- Even ones that support it. The MAJORITY of the cases, they can be completely avoided. In cases that aren't... You could just make a function-call... using return foo();

If you really want to understand... Just imagine Zodiac if goto's existed.

[projectigi]

Originally Posted by Novo

goto's are only useful ( really ) when you want to break out of two loop controls.

right, its quite annoying to check for a flag each time you have 2+ loops :P
or something like a breakall; that would just kill all the loops instead of the one you are in

basically what you're saying is kinda weird, that sounds like just because c++ has goto's every game only uses them instead of loops

[Skyld]

Originally Posted by projectigi

right, its quite annoying to check for a flag each time you have 2+ loops :P

How does that have anything to do with wanting "goto"?

Originally Posted by projectigi

or something like a breakall; that would just kill all the loops instead of the one you are in

It's called "return", and will end function execution there and then, regardless of how many loops you have.

[projectigi]

Originally Posted by Skyld

How does that have anything to do with wanting "goto"?

PHP Code:

for( foo = 0; foo < 100; foo++ )
  {
  for( bar  = 0; bar < 100; bar++ )
    {
    meh[ foo ][ bar ] = blub;
    if( /* do something that would exit the loop */ )
      goto( lEndL01 );
    }
  }
Label lEndL01:
//after loop 


Originally Posted by Skyld

It's called "return", and will end function execution there and then, regardless of how many loops you have.

you don't always want to end the whole function :P

[Skyld]

Originally Posted by projectigi

PHP Code:

for( foo = 0; foo < 100; foo++ )
  {
  for( bar  = 0; bar < 100; bar++ )
    {
    meh[ foo ][ bar ] = blub;
    if( /* do something that would exit the loop */ )
      goto( lEndL01 );
    }
  }
Label lEndL01:
//after loop 


you don't always want to end the whole function :P

Then structure your code better.

You could easily have those two loops in a function by themselves, and use "return" to end there, and send back the result of your function execution to the calling function.

[projectigi]

Originally Posted by Skyld

Then structure your code better.

You could easily have those two loops in a function by themselves, and use "return" to end there, and send back the result of your function execution to the calling function.

if i put every loop into a own function, reading a code with 1000+ lines will kinda be annoying lol

[zokemon]

Originally Posted by projectigi

if i put every loop into a own function, reading a code with 1000+ lines will kinda be annoying lol

Usually you can find a way to actually make it look better.

[zokemon]

Originally Posted by Skyld

It's called "return", and will end function execution there and then, regardless of how many loops you have.

Example:

PHP Code:

function onCreated() {
  foo = bar;
  var = 2;
  doLoop();
  doOtherThings();
}

function doLoop() {
  for (i = 0; i < 10; i++) {
    for (j = 0; j < 10; j++) {
      if (this.stuff[i][j])
        doLoopThings();
        return;
      }
    }
  }
}