in a loop

Code:

---

for (i=...)
  {
    .
    .
    if()
      "Iwant to take next i here"
    for (j=..)
    {
      .
      if()
        "I want also  next i here"
          .
          .
    }
  }

---

I want to get out of i and j loop when certain if is fulfilled but I want to avoid using goto command and I want to avoid restructuring loops.
Thank you

Code:

---

bool check;
for (i=...)
{
  check = false;
  if()
      //"I want to take next i here"
      continue;
  for (j=...;... && !check;)
  {
      if()
      {
        //"I want also  next i here"
        check = true;
        continue;
      }
  }
}

---

Here's another way..

Code:

---

for (i=...)
  {
    .
    .
    if()
      continue;  // "Iwant to take next i here"

    for (j=..)
    {
      .
      if()
        break;  // "I want also  next i here"
          .
          .
    }
  }

---

You'd need a little more work if there was more code after the j loop (while still inside i loop), but since you didn't list any, I will assume there isn't any, so this will work fine.

One thing I think the language really should have is an optional number after the break and continue statements, so you could have:

Code:

---

for (i=...) {
  for (j=...) {
      if (...)
        continue 2;  // go to next iteration of i
  }
}

---

So far, no one in charge of language design has ever thought of this idea though I guess. I put it in the scripting language I wrote, though.

continue just begins another iteration of the current loop. break breaks you out of the loop completely. Your wanting to use continue 2 would be the same as a break.

Additionally, people tend to forget that you can modify the sentinel from within the body of a loop. In the above examples, try coupling the continue/break statements with setting i or j to their sentinel values within the body of the loops, and see how well you can manipulate execution.

Quote:

---

Originally Posted by Scribbler

Additionally, people tend to forget that you can modify the sentinel from within the body of a loop.

---

It's not so much as a "forget" as a "prefer not to". Just as a matter of personal preference, I try to modify my loop control variables in only one place. It's just one less thing to think about when debugging long, complicated loops.

Quote:

---

It's not so much as a "forget" as a "prefer not to". Just as a matter of personal preference, I try to modify my loop control variables in only one place. It's just one less thing to think about when debugging long, complicated loops.

---

I have to agree there.

Isn't break 2; a valid statement? continue 2 would just move execution to the outer loop again. I've never actually tried using break 2 before but as far as I know it's valid.